Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 322296 - [DB] Missing some MYSQL Reserved Words for MySQL 5.1
Summary: [DB] Missing some MYSQL Reserved Words for MySQL 5.1
Status: CLOSED FIXED
Alias: None
Product: EMF
Classification: Modeling
Component: cdo.net4j.db (show other bugs)
Version: 4.10   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Stefan Winkler CLA
QA Contact: Eike Stepper CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-10 18:35 EDT by Heiko Ahlig CLA
Modified: 2020-12-11 10:32 EST (History)
1 user (show)

See Also:
stepper: documentation-


Attachments
added the new reserved words (1.88 KB, patch)
2010-08-10 18:37 EDT, Heiko Ahlig CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Heiko Ahlig CLA 2010-08-10 18:35:43 EDT
Build Identifier: I20100608-0911

The reserved words from the MySQL Adapter are incomplete.
Since version 5.1 the following words are also reserved:
 "ACCESSIBLE", "LINEAR", "MASTER_SSL_VERIFY_SERVER_CERT", "RANGE", "READ_ONLY", "READ_WRITE"

The other point is (what I doesnt tested today): 
It is usefull and doable to check, which version has MySQL server and after this build the complete liste of reserved words, because the MYSQL 5.5 and also some new reserved words?

Reproducible: Always
Comment 1 Heiko Ahlig CLA 2010-08-10 18:37:06 EDT
Created attachment 176285 [details]
added the new reserved words
Comment 2 Stefan Winkler CLA 2010-08-11 03:37:15 EDT
This overlaps with Bug 306356 which aims to eliminate the need to keep track of reserved words altogether by putting table and column names in quotes. This way, we also should eliminate the changing reserved words you mentioned.
Comment 3 Heiko Ahlig CLA 2010-09-15 16:50:58 EDT
Hi Stefan,
it's right, that finally the better way is your linked Bug.
But before somebody does fix this bug, my patch should fix some problems for users, which uses MySQL 5.1 and have also some of the missing words as attributes inside their models.
Comment 4 Eike Stepper CLA 2012-06-05 07:29:29 EDT
Moving all open bug reports to 4.1 because the release is very near and it's hghly unlikely that there will be spare time to address 4.0 problems.

Please make sure that your patches can be applied against the master branch and that your problem is not already fixed there!!!
Comment 5 Eike Stepper CLA 2012-08-14 22:51:04 EDT
Moving all open issues to 4.2. Open bugs can be ported to 4.1 maintenance after they've been fixed in master.
Comment 6 Eike Stepper CLA 2013-06-29 12:16:45 EDT
We'll try to address open problems in 4.3 (master) first and then port fixes back to 4.2.
Comment 7 Eike Stepper CLA 2015-07-14 02:08:41 EDT
Moving all open bugzillas to 4.5.
Comment 8 Eike Stepper CLA 2016-07-31 00:51:27 EDT
Moving all unaddressed bugzillas to 4.6.
Comment 9 Eike Stepper CLA 2017-12-28 01:11:58 EST
Moving all open bugs to 4.7
Comment 10 Eike Stepper CLA 2019-11-08 02:17:48 EST
Moving all unresolved issues to version 4.8-
Comment 11 Eike Stepper CLA 2019-12-13 12:51:57 EST
Moving all unresolved issues to version 4.9
Comment 12 Eike Stepper CLA 2020-04-03 04:05:57 EDT
I assume that this is fixed now with the changes of bug 546872.
Comment 13 Eike Stepper CLA 2020-12-11 10:24:06 EST
Closing.
Comment 14 Eike Stepper CLA 2020-12-11 10:32:18 EST
Closing.