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.

Bug 121016 - Support for autogenerated keys in Derby
Summary: Support for autogenerated keys in Derby
Status: RESOLVED DUPLICATE of bug 57979
Alias: None
Product: db
Classification: Unclassified
Component: Derby (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Libor Fischmeistr
URL:
Keywords:
Depends on:
Blocks: 152850
  Show dependency tree
 
Reported: 2007-11-02 19:03 UTC by antodasana
Modified: 2014-09-23 19:00 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description antodasana 2007-11-02 19:03:38 UTC 
Working with a derby connection in Runtime window, creating a new column, I miss the capacity of creating autogenerated
keys (IDENTITY columns in Derby) from the GUI.

On the opposite direction, when creating my JPA persistent entity beans from a Derby database, the autogeneration
capability is not recognized, and I must type the annotation '@GeneratedValue(strategy=GenerationType.IDENTITY)' in all
entities with identity columns. This annotation is required in order to be able to persist entities in the database.

I think this would help to many developers.
Comment 1 Jiri Rechtacek 2009-10-16 14:05:58 UTC 
Reassigned to new owner.
Comment 2 matthias42 2014-09-23 19:00:22 UTC 

*** This bug has been marked as a duplicate of bug 57979 ***