Issue 13801 - cannot edit / insert record when more or less than one primary key defined
Summary: cannot edit / insert record when more or less than one primary key defined
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 Beta
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Frank Schönheit
QA Contact: issues@dba
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-25 08:44 UTC by pachollini
Modified: 2006-05-31 14:29 UTC (History)
1 user (show)

See Also:
Issue Type: TASK
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 pachollini 2003-04-25 08:44:10 UTC 
I'm not sure, if this is a bug or just a thing to do, but I find it quite
important: I work with more MySQL tables I quite often I have more than one
culomn defined as primary key. In such cases it is not possible to insert and
edit records in OOo. 
Similarily, it is not possible to edit / insert records on tables where no
primary key is defined, but I don't find this as a bug - every table can or
should have an index...
This is maybe similar to issue #12055
Comment 1 pachollini 2003-04-25 08:56:14 UTC 
sorry, my mistake
Comment 2 Frank Schönheit 2003-04-25 09:21:05 UTC 
pachollini, please also close the issue then - thanks :)
Comment 3 Frank Schönheit 2003-05-20 12:11:51 UTC 
closing
Comment 4 hans_werner67 2004-02-02 13:04:35 UTC 
change subcomponent to 'none'