This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Product Version: NetBeans IDE 6.5 (Build 200811100001) Java: 1.6.0_10; Java HotSpot(TM) Client VM 11.0-b15 System: Windows Vista version 6.0 running on x86; Cp1250; cs_CZ (nb) Observed: I created entity classes from the database. One table had name group, so I must choose anotoher name and I choose Groups. After I opened this entity class and there was error "The entity table name is a reserved Java Persistence QL keyword.", but when I erase "s" in word Groups and write it there again and save this document, error is gone. The error appears everytime when I open this class again.
also see issue 147368
What database did you use? "group" is an invalid database table name.
I'm using MySQL5 database.
may be a duplicate of issue 153944
reproducible in 6.8(091001), except alternative name, it was automatically generated as 'Group1'
and error isn't gone away after edition.
neither toplink nor eclipselink nor hibernate can't persist this object. so even if this one minor issue will be fixed and there will be no error badges, in real application this entity/table will fail to work properly. also it may be hard to have general fix for all kind of databases as mysql require `` for such table names, others databased may require "" etc. for example see https://bugs.eclipse.org/bugs/show_bug.cgi?id=271782 I'm not sure if it's good just to remove this error badge but in my opinion it's not even p3 as it's anyway not usable entity and user is notified about problems, may be as a fix message should be about SQL reserved work instead of EJB QL and badge should point to entity annotation if entity annotation exist to be more clear. Also from my expirience there are almost no restictions on entity names itself, for example next ejb ql works 'select count(o) from as as o'. and it means fix should be just to change "reserved Java Persistence QL" with "reserved SQL keyword".
decided to fix in 6.8 as already found all related to the issue: http://hg.netbeans.org/web-main/rev/efd72dbbff17 http://hg.netbeans.org/web-main/rev/95488db712be http://hg.netbeans.org/web-main/rev/433f38ebf1f4 now first table foe SQL keyword is verified as it cause problems with all (almost all) providers and a some databases. next entity name is verified for EJB QL keyword, but it's warning now, not error as there seems to be no real restictions according to spec and verification with eclipselink 2.0.
Integrated into 'main-golden', will be available in build *200910030241* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/efd72dbbff17 User: sergeyp@netbeans.org Log: fix #154149 - as in real table name is verified. Also according to tests with eclipselink and from specification "Reserved identifiers must not be used as identification variables or result variables" it seems there should be no restrictions on entity name itself only on identifiers in EJB QL queries. do not remove ejb ql check completely but check for sql first and mark as SQL reserved then. conside later remove EJB QL verification here.
Integrated into 'main-golden', will be available in build *200910061401* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/efd72dbbff17 User: sergeyp@netbeans.org Log: fix #154149 - as in real table name is verified. Also according to tests with eclipselink and from specification "Reserved identifiers must not be used as identification variables or result variables" it seems there should be no restrictions on entity name itself only on identifiers in EJB QL queries. do not remove ejb ql check completely but check for sql first and mark as SQL reserved then. conside later remove EJB QL verification here.