You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <de...@db.apache.org> on 2006/09/07 02:14:22 UTC
[jira] Created: (DERBY-1822) LOCK TABLE example and description in
reference manual should get replaced by a 'real' example
LOCK TABLE example and description in reference manual should get replaced by a 'real' example
----------------------------------------------------------------------------------------------
Key: DERBY-1822
URL: http://issues.apache.org/jira/browse/DERBY-1822
Project: Derby
Issue Type: Bug
Components: Documentation
Affects Versions: 10.2.1.0, 10.3.0.0
Reporter: Myrna van Lunteren
Priority: Minor
Fix For: 10.3.0.0
The Example in the documentation for LOCK TABLE looks jumbled.
It looks like part of it is based on a demo that was part of the pre-quel to Derby. The current toursdb demo is based on it, and thus includes reference to the table 'Flights', so it looks as if the queries *might* be possible, but the table listed (HotelAvailability) does not exist.
Then there is mention of the table People, which doesn't exist either,
A proper example needs to be put in place.
Note that the description above the example mentions Hotels, this probably was supposed to be removed also.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1822) LOCK TABLE example and description
in reference manual should get replaced by a 'real' example
Posted by "Mamta A. Satoor (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1822?page=comments#action_12438514 ]
Mamta A. Satoor commented on DERBY-1822:
----------------------------------------
Laura, I looked at the latest patch and following line needs rewording.
"To lock the entire FlightsAvailable table in exclusive mode for a transaction that will update many rows, but where no single statement will update enough rows, acquire an exclusive table lock on the table. "
Here is what the example is trying to do, please feel free to word it as seems appropriate.
Consider a trasnaction with multiple update statements, each one of which acquires couple row locks here and there. Since each individual update statement acquires only few row level locks, the transaction will not automatically upgrade the locks to a table level lock. But all of the update statements collectively endup getting and releasing large number of locks and may even run into deadlocks. For such transactions, it might be better to just acquire a table level lock at the beginning of the transaction. This way, individual updatement statements won't have to keep acquiring and releasing row level locks.
One suggestion for the rewording of the above statement
"Lock the entire FlightsAvailable table in exclusive mode for the transaction that will update many rows, but where no single update statement will update enough rows to acquire an exclusive table lock on the table. "
> LOCK TABLE example and description in reference manual should get replaced by a 'real' example
> ----------------------------------------------------------------------------------------------
>
> Key: DERBY-1822
> URL: http://issues.apache.org/jira/browse/DERBY-1822
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.2.1.5, 10.3.0.0
> Reporter: Myrna van Lunteren
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1822.diff, derby1822_2.diff, rrefsqlj40506.html, rrefsqlj40506.html
>
>
> The Example in the documentation for LOCK TABLE looks jumbled.
> It looks like part of it is based on a demo that was part of the pre-quel to Derby. The current toursdb demo is based on it, and thus includes reference to the table 'Flights', so it looks as if the queries *might* be possible, but the table listed (HotelAvailability) does not exist.
> Then there is mention of the table People, which doesn't exist either,
> A proper example needs to be put in place.
> Note that the description above the example mentions Hotels, this probably was supposed to be removed also.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (DERBY-1822) LOCK TABLE example and description in
reference manual should get replaced by a 'real' example
Posted by "Laura Stewart (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1822?page=all ]
Laura Stewart resolved DERBY-1822.
----------------------------------
Resolution: Fixed
Derby Info: (was: [Patch Available])
Changing the status to resolved.
Not closing this issue until Rick (or someone else) commits it to the 10.2 trunk.
> LOCK TABLE example and description in reference manual should get replaced by a 'real' example
> ----------------------------------------------------------------------------------------------
>
> Key: DERBY-1822
> URL: http://issues.apache.org/jira/browse/DERBY-1822
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.2.1.5, 10.3.0.0
> Reporter: Myrna van Lunteren
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1822.diff, derby1822_2.diff, derby1822_3.diff, rrefsqlj40506.html, rrefsqlj40506.html, rrefsqlj40506.html
>
>
> The Example in the documentation for LOCK TABLE looks jumbled.
> It looks like part of it is based on a demo that was part of the pre-quel to Derby. The current toursdb demo is based on it, and thus includes reference to the table 'Flights', so it looks as if the queries *might* be possible, but the table listed (HotelAvailability) does not exist.
> Then there is mention of the table People, which doesn't exist either,
> A proper example needs to be put in place.
> Note that the description above the example mentions Hotels, this probably was supposed to be removed also.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1822) LOCK TABLE example and description
in reference manual should get replaced by a 'real' example
Posted by "Laura Stewart (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1822?page=comments#action_12434219 ]
Laura Stewart commented on DERBY-1822:
--------------------------------------
Can someone please take a look at the current example
http://db.apache.org/derby/docs/dev/ref/rrefsqlj40506.html
and please post a new example?
The documentation can then be updated.
> LOCK TABLE example and description in reference manual should get replaced by a 'real' example
> ----------------------------------------------------------------------------------------------
>
> Key: DERBY-1822
> URL: http://issues.apache.org/jira/browse/DERBY-1822
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.2.1.0, 10.3.0.0
> Reporter: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.3.0.0
>
>
> The Example in the documentation for LOCK TABLE looks jumbled.
> It looks like part of it is based on a demo that was part of the pre-quel to Derby. The current toursdb demo is based on it, and thus includes reference to the table 'Flights', so it looks as if the queries *might* be possible, but the table listed (HotelAvailability) does not exist.
> Then there is mention of the table People, which doesn't exist either,
> A proper example needs to be put in place.
> Note that the description above the example mentions Hotels, this probably was supposed to be removed also.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1822) LOCK TABLE example and description
in reference manual should get replaced by a 'real' example
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1822?page=comments#action_12438563 ]
Andrew McIntyre commented on DERBY-1822:
----------------------------------------
Committed to trunk with revision 451037.
> LOCK TABLE example and description in reference manual should get replaced by a 'real' example
> ----------------------------------------------------------------------------------------------
>
> Key: DERBY-1822
> URL: http://issues.apache.org/jira/browse/DERBY-1822
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.2.1.5, 10.3.0.0
> Reporter: Myrna van Lunteren
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1822.diff, derby1822_2.diff, derby1822_3.diff, rrefsqlj40506.html, rrefsqlj40506.html, rrefsqlj40506.html
>
>
> The Example in the documentation for LOCK TABLE looks jumbled.
> It looks like part of it is based on a demo that was part of the pre-quel to Derby. The current toursdb demo is based on it, and thus includes reference to the table 'Flights', so it looks as if the queries *might* be possible, but the table listed (HotelAvailability) does not exist.
> Then there is mention of the table People, which doesn't exist either,
> A proper example needs to be put in place.
> Note that the description above the example mentions Hotels, this probably was supposed to be removed also.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1822) LOCK TABLE example and description in
reference manual should get replaced by a 'real' example
Posted by "Laura Stewart (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1822?page=all ]
Laura Stewart updated DERBY-1822:
---------------------------------
Derby Info: [Patch Available]
> LOCK TABLE example and description in reference manual should get replaced by a 'real' example
> ----------------------------------------------------------------------------------------------
>
> Key: DERBY-1822
> URL: http://issues.apache.org/jira/browse/DERBY-1822
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.2.1.5, 10.3.0.0
> Reporter: Myrna van Lunteren
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1822.diff, rrefsqlj40506.html
>
>
> The Example in the documentation for LOCK TABLE looks jumbled.
> It looks like part of it is based on a demo that was part of the pre-quel to Derby. The current toursdb demo is based on it, and thus includes reference to the table 'Flights', so it looks as if the queries *might* be possible, but the table listed (HotelAvailability) does not exist.
> Then there is mention of the table People, which doesn't exist either,
> A proper example needs to be put in place.
> Note that the description above the example mentions Hotels, this probably was supposed to be removed also.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (DERBY-1822) LOCK TABLE example and description in
reference manual should get replaced by a 'real' example
Posted by "Laura Stewart (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1822?page=all ]
Laura Stewart reassigned DERBY-1822:
------------------------------------
Assignee: Laura Stewart
> LOCK TABLE example and description in reference manual should get replaced by a 'real' example
> ----------------------------------------------------------------------------------------------
>
> Key: DERBY-1822
> URL: http://issues.apache.org/jira/browse/DERBY-1822
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.2.1.5, 10.3.0.0
> Reporter: Myrna van Lunteren
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
>
> The Example in the documentation for LOCK TABLE looks jumbled.
> It looks like part of it is based on a demo that was part of the pre-quel to Derby. The current toursdb demo is based on it, and thus includes reference to the table 'Flights', so it looks as if the queries *might* be possible, but the table listed (HotelAvailability) does not exist.
> Then there is mention of the table People, which doesn't exist either,
> A proper example needs to be put in place.
> Note that the description above the example mentions Hotels, this probably was supposed to be removed also.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1822) LOCK TABLE example and description
in reference manual should get replaced by a 'real' example
Posted by "Myrna van Lunteren (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1822?page=comments#action_12438247 ]
Myrna van Lunteren commented on DERBY-1822:
-------------------------------------------
I tried the text as it appears in the .html attached and ij noticed 'SET' has wandered off in the first UPDATE FlightAvailability statement:
LOCK TABLE FlightAvailability IN EXCLUSIVE MODE;
UPDATE FlightAvailability
[..should have: SET]-> economy_seats_taken = (economy_seats_taken + 2)
WHERE flight_id = 'AA1265' AND flight_date = DATE('2004-03-31');
> LOCK TABLE example and description in reference manual should get replaced by a 'real' example
> ----------------------------------------------------------------------------------------------
>
> Key: DERBY-1822
> URL: http://issues.apache.org/jira/browse/DERBY-1822
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.2.1.5, 10.3.0.0
> Reporter: Myrna van Lunteren
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1822.diff, rrefsqlj40506.html
>
>
> The Example in the documentation for LOCK TABLE looks jumbled.
> It looks like part of it is based on a demo that was part of the pre-quel to Derby. The current toursdb demo is based on it, and thus includes reference to the table 'Flights', so it looks as if the queries *might* be possible, but the table listed (HotelAvailability) does not exist.
> Then there is mention of the table People, which doesn't exist either,
> A proper example needs to be put in place.
> Note that the description above the example mentions Hotels, this probably was supposed to be removed also.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1822) LOCK TABLE example and description
in reference manual should get replaced by a 'real' example
Posted by "Mamta A. Satoor (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1822?page=comments#action_12438181 ]
Mamta A. Satoor commented on DERBY-1822:
----------------------------------------
Laura, I took a look at the page and the current structure of toursdb and have come up with following example that can be used on the LOCK TABLE page. Hope this helps
1)First of all, there is a typo in the first paragraph under Syntax. Rather than 'Hotels', it should say 'Fights'. It should read as following
"Once a table is locked in either mode, a transaction does not acquire any subsequent row-level locks on a table. For example, if a transaction locks the entire Flights table in share mode in order to read data, a particular statement might need to lock a particular row in exclusive mode in order to update the row. However, the previous table-level lock on Flights forces the exclusive lock to be table-level as well."
2)The updated example can look as follows
-- lock the entire table in share mode to avoid
-- a large number of row locks
LOCK TABLE Flights IN SHARE MODE;
SELECT *
FROM Flights
WHERE orig_airport > 'OOO';
-- lock the entire table in exclusive mode
-- for a transaction that will update many rows,
-- but where no single statement will update enough rows
-- to acquire an exclusive table lock on the table.
-- In a row-level locking system, that transaction would
-- require a large number of locks or might deadlock.
LOCK TABLE FlightAvailability IN EXCLUSIVE MODE;
UPDATE FlightAvailability
SET economy_seats_taken = (economy_seats_taken + 2)
WHERE flight_id = 'AA1265' AND flight_date = DATE('2004-03-31');
UPDATE FlightAvailability
SET economy_seats_taken = (economy_seats_taken + 2)
WHERE flight_id = 'AA1265' AND flight_date = DATE('2004-04-11');
UPDATE FlightAvailability
SET economy_seats_taken = (economy_seats_taken + 2)
WHERE flight_id = 'AA1265' AND flight_date = DATE('2004-04-12');
UPDATE FlightAvailability
SET economy_seats_taken = (economy_seats_taken + 2)
WHERE flight_id = 'AA1265' AND flight_date = DATE('2004-04-15');
-- if a transaction needs to look at a table before
-- updating it, acquire an exclusive lock before
-- selecting to avoid deadlocks
LOCK TABLE Maps IN EXCLUSIVE MODE;
SELECT MAX(map_id) + 1 from Maps;
-- INSERT INTO MAPS . . .
> LOCK TABLE example and description in reference manual should get replaced by a 'real' example
> ----------------------------------------------------------------------------------------------
>
> Key: DERBY-1822
> URL: http://issues.apache.org/jira/browse/DERBY-1822
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.2.1.5, 10.3.0.0
> Reporter: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.3.0.0
>
>
> The Example in the documentation for LOCK TABLE looks jumbled.
> It looks like part of it is based on a demo that was part of the pre-quel to Derby. The current toursdb demo is based on it, and thus includes reference to the table 'Flights', so it looks as if the queries *might* be possible, but the table listed (HotelAvailability) does not exist.
> Then there is mention of the table People, which doesn't exist either,
> A proper example needs to be put in place.
> Note that the description above the example mentions Hotels, this probably was supposed to be removed also.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1822) LOCK TABLE example and description
in reference manual should get replaced by a 'real' example
Posted by "Mamta A. Satoor (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1822?page=comments#action_12438561 ]
Mamta A. Satoor commented on DERBY-1822:
----------------------------------------
Laura, I looked through the text change for the examples and it looks good to me. +1 for commit from me.
> LOCK TABLE example and description in reference manual should get replaced by a 'real' example
> ----------------------------------------------------------------------------------------------
>
> Key: DERBY-1822
> URL: http://issues.apache.org/jira/browse/DERBY-1822
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.2.1.5, 10.3.0.0
> Reporter: Myrna van Lunteren
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1822.diff, derby1822_2.diff, derby1822_3.diff, rrefsqlj40506.html, rrefsqlj40506.html, rrefsqlj40506.html
>
>
> The Example in the documentation for LOCK TABLE looks jumbled.
> It looks like part of it is based on a demo that was part of the pre-quel to Derby. The current toursdb demo is based on it, and thus includes reference to the table 'Flights', so it looks as if the queries *might* be possible, but the table listed (HotelAvailability) does not exist.
> Then there is mention of the table People, which doesn't exist either,
> A proper example needs to be put in place.
> Note that the description above the example mentions Hotels, this probably was supposed to be removed also.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1822) LOCK TABLE example and description in
reference manual should get replaced by a 'real' example
Posted by "Laura Stewart (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1822?page=all ]
Laura Stewart updated DERBY-1822:
---------------------------------
Attachment: derby1822.diff
rrefsqlj40506.html
Updated the example and corrected the errors.
I also gave the examples a title and did some minor formatting.
> LOCK TABLE example and description in reference manual should get replaced by a 'real' example
> ----------------------------------------------------------------------------------------------
>
> Key: DERBY-1822
> URL: http://issues.apache.org/jira/browse/DERBY-1822
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.2.1.5, 10.3.0.0
> Reporter: Myrna van Lunteren
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1822.diff, rrefsqlj40506.html
>
>
> The Example in the documentation for LOCK TABLE looks jumbled.
> It looks like part of it is based on a demo that was part of the pre-quel to Derby. The current toursdb demo is based on it, and thus includes reference to the table 'Flights', so it looks as if the queries *might* be possible, but the table listed (HotelAvailability) does not exist.
> Then there is mention of the table People, which doesn't exist either,
> A proper example needs to be put in place.
> Note that the description above the example mentions Hotels, this probably was supposed to be removed also.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1822) LOCK TABLE example and description in
reference manual should get replaced by a 'real' example
Posted by "Laura Stewart (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1822?page=all ]
Laura Stewart updated DERBY-1822:
---------------------------------
Attachment: derby1822_2.diff
rrefsqlj40506.html
Added SET to the example :-)
Good catch Myrna !
New diff and html.zip file attached.
> LOCK TABLE example and description in reference manual should get replaced by a 'real' example
> ----------------------------------------------------------------------------------------------
>
> Key: DERBY-1822
> URL: http://issues.apache.org/jira/browse/DERBY-1822
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.2.1.5, 10.3.0.0
> Reporter: Myrna van Lunteren
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1822.diff, derby1822_2.diff, rrefsqlj40506.html, rrefsqlj40506.html
>
>
> The Example in the documentation for LOCK TABLE looks jumbled.
> It looks like part of it is based on a demo that was part of the pre-quel to Derby. The current toursdb demo is based on it, and thus includes reference to the table 'Flights', so it looks as if the queries *might* be possible, but the table listed (HotelAvailability) does not exist.
> Then there is mention of the table People, which doesn't exist either,
> A proper example needs to be put in place.
> Note that the description above the example mentions Hotels, this probably was supposed to be removed also.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1822) LOCK TABLE example and description in
reference manual should get replaced by a 'real' example
Posted by "Laura Stewart (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1822?page=all ]
Laura Stewart updated DERBY-1822:
---------------------------------
Attachment: derby1822_3.diff
rrefsqlj40506.html
Glad you explained it to me. I did not like the original wording either :-)
I have updated the file and create a new patch (#3).
Look for the most recent date for the current html file.
> LOCK TABLE example and description in reference manual should get replaced by a 'real' example
> ----------------------------------------------------------------------------------------------
>
> Key: DERBY-1822
> URL: http://issues.apache.org/jira/browse/DERBY-1822
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.2.1.5, 10.3.0.0
> Reporter: Myrna van Lunteren
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1822.diff, derby1822_2.diff, derby1822_3.diff, rrefsqlj40506.html, rrefsqlj40506.html, rrefsqlj40506.html
>
>
> The Example in the documentation for LOCK TABLE looks jumbled.
> It looks like part of it is based on a demo that was part of the pre-quel to Derby. The current toursdb demo is based on it, and thus includes reference to the table 'Flights', so it looks as if the queries *might* be possible, but the table listed (HotelAvailability) does not exist.
> Then there is mention of the table People, which doesn't exist either,
> A proper example needs to be put in place.
> Note that the description above the example mentions Hotels, this probably was supposed to be removed also.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-1822) LOCK TABLE example and description in
reference manual should get replaced by a 'real' example
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1822?page=all ]
Andrew McIntyre closed DERBY-1822.
----------------------------------
Merged to 10.2 with revision 451427.
> LOCK TABLE example and description in reference manual should get replaced by a 'real' example
> ----------------------------------------------------------------------------------------------
>
> Key: DERBY-1822
> URL: http://issues.apache.org/jira/browse/DERBY-1822
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.2.1.5, 10.3.0.0
> Reporter: Myrna van Lunteren
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1822.diff, derby1822_2.diff, derby1822_3.diff, rrefsqlj40506.html, rrefsqlj40506.html, rrefsqlj40506.html
>
>
> The Example in the documentation for LOCK TABLE looks jumbled.
> It looks like part of it is based on a demo that was part of the pre-quel to Derby. The current toursdb demo is based on it, and thus includes reference to the table 'Flights', so it looks as if the queries *might* be possible, but the table listed (HotelAvailability) does not exist.
> Then there is mention of the table People, which doesn't exist either,
> A proper example needs to be put in place.
> Note that the description above the example mentions Hotels, this probably was supposed to be removed also.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira