Issue 64408 - Can't set primary keys for derby/java db databases
Summary: Can't set primary keys for derby/java db databases
Status: UNCONFIRMED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 2.0.2
Hardware: PC Windows XP
: P4 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-14 21:37 UTC by cbulcu
Modified: 2013-02-07 22:33 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---

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

Note You need to log in before you can comment on or make changes to this issue.
Description cbulcu 2006-04-14 21:37:30 UTC 
I created a table in a embedded derby database. I opened the contextual pop-up
menu to set the primary key, and there was nothing. The docs say that when that
menu item doesn't appear, then the db doesn't support primary keys. But you know
that derby supports them.
Comment 1 christoph.lukasiak 2006-05-09 14:36:02 UTC 
clu->cbulcu: both is right - when oo connect to a foreign datasource, it asks
your driver (odbc/jdbc/ado) if the connected database support primary keys: if
the driver give back a 'no' then this option is not available over the ui,
doesen't matter if the database itselve support primary keys - maybe with an
other driver or next version of your driver this will work as expected

clu->protocol: this is on of many databases/driver combination that partly does
not work as expected with oo because of partly ignoring standards - like with
mysql this can be trick out internaly => send to: requirements
Comment 2 christoph.lukasiak 2006-05-09 14:46:22 UTC 
clu->cbulcu: may you add the version number of the database that you connect and
for the used driver

thx
Comment 3 cbulcu 2006-05-09 17:35:06 UTC 
Apache Derby 10.1.2.1 Release