[
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
