You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-commits@db.apache.org by rh...@apache.org on 2010/04/20 19:23:00 UTC
svn commit: r936006 - in /db/derby/code/trunk: RELEASE-NOTES.html
java/build/org/apache/derbyBuild/JiraIssue.java releaseSummary.xml
Author: rhillegas
Date: Tue Apr 20 17:22:59 2010
New Revision: 936006
URL: http://svn.apache.org/viewvc?rev=936006&view=rev
Log:
DERBY-4593: Small changes to release notes based on community feedback.
Modified:
db/derby/code/trunk/RELEASE-NOTES.html
db/derby/code/trunk/java/build/org/apache/derbyBuild/JiraIssue.java
db/derby/code/trunk/releaseSummary.xml
Modified: db/derby/code/trunk/RELEASE-NOTES.html
URL: http://svn.apache.org/viewvc/db/derby/code/trunk/RELEASE-NOTES.html?rev=936006&r1=936005&r2=936006&view=diff
==============================================================================
--- db/derby/code/trunk/RELEASE-NOTES.html (original)
+++ db/derby/code/trunk/RELEASE-NOTES.html Tue Apr 20 17:22:59 2010
@@ -87,7 +87,7 @@ This is a feature release. The following
<li>
-<b>CROSS JOIN</b> - CROSS JOIN syntax. See features F401-04 of the SQL Standard.</li>
+<b>CROSS JOIN</b> - CROSS JOIN syntax. See feature F401-04 of the SQL Standard.</li>
<li>
@@ -1610,8 +1610,7 @@ CROSS is now a reserved keyword and cann
<li>
<a href="#Note for DERBY-4312">
<p>Note for DERBY-4312:
-After the change for DERBY-4312, if a user attempts to reuse a stream set on a <code> PreparedStatement </code> with <code> setAsciiStream()</code>, <code>setCharacterStream()</code>, or <code> setBinaryStream() </code> after commit, the incorrect error XJ215 will no longer be thrown. Because of this, users attempting to reuse streams may be exposed to DERBY-4315 - Attempt to reuse streams in client on insert gives protocol exception and inserts wrong data.
-
+Stream re-use problems now more likely.
</p>
</a>
</li>
@@ -1625,7 +1624,7 @@ After the change for DERBY-4312, if a us
<li>
<a href="#Note for DERBY-4191">
<p>Note for DERBY-4191:
-Make sure that user has at least one column level select privilege or table level select privilege for queries that do not select a specific column from the tables involved in the SELECT statement. Additionally, subqueries will require that the user has necessary select privileges in order to execute it.
+Some queries require additional SELECT privileges now.
</p>
</a>
</li>
@@ -2357,8 +2356,7 @@ to <code>select * from "CROSS"</code>.
<h4>Summary of Change</h4>
<p>
-After the change for DERBY-4312, if a user attempts to reuse a stream set on a <code> PreparedStatement </code> with <code> setAsciiStream()</code>, <code>setCharacterStream()</code>, or <code> setBinaryStream() </code> after commit, the incorrect error XJ215 will no longer be thrown. Because of this, users attempting to reuse streams may be exposed to DERBY-4315 - Attempt to reuse streams in client on insert gives protocol exception and inserts wrong data.
-
+Stream re-use problems now more likely.
</p>
@@ -2553,31 +2551,93 @@ Users must drop an recreate affected vie
<h4>Summary of Change</h4>
<p>
-Make sure that user has at least one column level select privilege or table level select privilege for queries that do not select a specific column from the tables involved in the SELECT statement. Additionally, subqueries will require that the user has necessary select privileges in order to execute it.
+Some queries require additional SELECT privileges now.
</p>
-<!--
- In the previous release, because of Derby bug, users were able to do selects from table even when they didn't have select privilege available on it. For eg the query below in previous release would succeed even if the user didn't have any select privilege on anotheruser.table1
+
+<h4>Symptoms Seen by Applications Affected by Change</h4>
+
+<p>
+In previous releases, certain queries incorrectly succeeded when the
+user lacked sufficient SELECT privileges. For instance, the following
+query succeeded even if the user did not have SELECT privilege on the table:
+</p>
+
+
+<blockquote>
+<pre>
select 1 from anotheruser.table1
- Also, in the previous release, following query executed fine even if the user had only update privilege available on anotheruser.table1
+</pre>
+</blockquote>
+
+
+<p>
+And the following query succeeded if the user had UPDATE but not
+SELECT privilege on the column:
+</p>
+
+
+<blockquote>
+<pre>
update anotheruser.table1 set a = ( select max(a) + 2 from anotheruser.table1 );
- Now, Derby raises a SQLException for those missing select privileges.
+</pre>
+</blockquote>
+
+<!--
+ OPTIONAL: DESCRIBE INCOMPATIBILITIES WITH PREVIOUS RELEASE, IF ANY.
+
+ For instance:
+
+ Applications which open two InputStreams on the ResultSet column now
+ fail.
-->
-<h4>Symptoms Seen by Applications Affected by Change</h4>
+<h4>Incompatibilities with Previous Release</h4>
<p>
-Previous release incorrectly allowed a query execution despite insufficient privileges.
+Now Derby raises a SQLException for those situations. For the first
+query above, the user must now enjoy SELECT privilege on at least one
+column in the table. For the second query, the user must now enjoy
+SELECT as well as UPDATE privilege on the affected column.
</p>
<!--
- The previous behavior incorrectly allowed users to execute a query even when the necessary privileges were not granted to them.
+ DESCRIBE WHY THE CHANGE WAS MADE.
+
+ For instance:
+
+ The previous behavior violated the JDBC standard. The new behavior
+ is correct.
-->
+<h4>Rationale for Change</h4>
+
+<p>
+The old behavior violated the SQL Standard. The new behavior is correct.
+</p>
+
+
+<!--
+ OPTIONAL: DESCRIBE HOW TO REVERT TO THE PREVIOUS BEHAVIOR OR
+ OTHERWISE AVOID THE INCOMPATIBILITIES INTRODUCED BY THIS CHANGE.
+
+ For instance:
+
+ Users must recode applications which open multiple streams on the same column.
+-->
+
+
+<h4>Application Changes Required</h4>
+
+<p>
+Database Administrators may need to grant users additional SELECT privileges.
+</p>
+
+
</blockquote>
<hr>
Modified: db/derby/code/trunk/java/build/org/apache/derbyBuild/JiraIssue.java
URL: http://svn.apache.org/viewvc/db/derby/code/trunk/java/build/org/apache/derbyBuild/JiraIssue.java?rev=936006&r1=936005&r2=936006&view=diff
==============================================================================
--- db/derby/code/trunk/java/build/org/apache/derbyBuild/JiraIssue.java (original)
+++ db/derby/code/trunk/java/build/org/apache/derbyBuild/JiraIssue.java Tue Apr 20 17:22:59 2010
@@ -66,7 +66,10 @@ class JiraIssue {
for (Iterator i = ef.getTextListByTagName(JIRA_FIXVERSION).iterator();
i.hasNext();) {
- fixVersionSet.add(i.next());
+
+ String nextVersion = (String) i.next();
+
+ fixVersionSet.add( nextVersion );
}
}
@@ -108,9 +111,9 @@ class JiraIssue {
else if ( key.equals( "DERBY-4432" ) ) { result = 12424709L; }
else if ( key.equals( "DERBY-4380" ) ) { result = 12434514L; }
else if ( key.equals( "DERBY-4355" ) ) { result = 12419298L; }
- else if ( key.equals( "DERBY-4312" ) ) { result = 12414219L; }
+ else if ( key.equals( "DERBY-4312" ) ) { result = 12442288L; }
else if ( key.equals( "DERBY-4230" ) ) { result = 12409466L; }
- else if ( key.equals( "DERBY-4191" ) ) { result = 12430699L; }
+ else if ( key.equals( "DERBY-4191" ) ) { result = 12442312L; }
else if ( key.equals( "DERBY-3991" ) ) { result = 12409798L; }
else if ( key.equals( "DERBY-3844" ) ) { result = 12436979L; }
else if ( key.equals( "DERBY-2769" ) ) { result = 12418474L; }
Modified: db/derby/code/trunk/releaseSummary.xml
URL: http://svn.apache.org/viewvc/db/derby/code/trunk/releaseSummary.xml?rev=936006&r1=936005&r2=936006&view=diff
==============================================================================
--- db/derby/code/trunk/releaseSummary.xml (original)
+++ db/derby/code/trunk/releaseSummary.xml Tue Apr 20 17:22:59 2010
@@ -47,6 +47,7 @@ with real information.
<excludeReleaseID>10.4.1.3</excludeReleaseID>
<excludeReleaseID>10.4.2.0</excludeReleaseID>
<excludeReleaseID>10.5.1.1</excludeReleaseID>
+<excludeReleaseID>10.5.2.0</excludeReleaseID>
<excludeReleaseID>10.5.3.0</excludeReleaseID>
<buildInfo>
@@ -119,7 +120,7 @@ This is a feature release. The following
<li><b>GROUP BY ROLLUP</b> - A subset of the SQL Standard ROLLUP functionality on the GROUP BY clause. See feature T431 of the SQL Standard.</li>
-<li><b>CROSS JOIN</b> - CROSS JOIN syntax. See features F401-04 of the SQL Standard.</li>
+<li><b>CROSS JOIN</b> - CROSS JOIN syntax. See feature F401-04 of the SQL Standard.</li>
<li><b>Named columns join</b> - USING clauses in joins.</li>