Issue 12553 - edit DB table
Summary: edit DB table
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.2
Hardware: PC Windows XP
: P1 (highest) Trivial (vote)
Target Milestone: ---
Assignee: Frank Schönheit
QA Contact: issues@dba
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-21 12:16 UTC by marting
Modified: 2006-05-31 14:29 UTC (History)
1 user (show)

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

Attachments
table edit problem (7.16 KB, image/png)
2003-03-21 12:17 UTC, marting 		no flags Details
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 marting 2003-03-21 12:16:32 UTC 
the created tables cannot be published !

see screenshot

salut,
marting
Comment 1 marting 2003-03-21 12:17:18 UTC 
Created attachment 5188 [details]
table edit problem
Comment 2 Frank Schönheit 2003-03-22 10:43:07 UTC 
Martin, this is no bug - if the database tells that it is not capable
of changing existent columns, then OOo does prevent you from doing this.

Because you did not tell us anything about the database you are
working with, I can only guess, but for instance, MySQL is such a
database which does not allow (at least it _tells_ OOo that it does
not allow!) to change existing table columns.
Comment 3 marting 2003-03-24 10:23:15 UTC 
mmm...
yes, im use a MySQL 3.23.49-max-nt in WinXP(sorry)
 
Q: in the future OO it will be able to modify the columns?
Q: in the future OO it will be able to login as root or other register
user in MySQL?

tnx,
marting
Comment 4 Frank Schönheit 2003-03-24 15:35:35 UTC 
> Q: in the future OO it will be able to modify the columns?

The only possible option for OOo would be an option (!) like "ignore
what the driver actually tells you", then changing columns would
either fail with a database error, or succeed in case the database
driver told nonsense.
Maybe this will be implemented, I am pretty indetermined about this.

> Q: in the future OO it will be able to login as root or other
> register user in MySQL?

No. If the missing privileges of the user which you used for login is
everything which prevents you from editing, then login as a different
user :). Means: Provided that you logged in as user A, and A does not
have privileges to alter tables, then OOo will not automatically log
in as root. Instead, you can (and should, consequently) then login as
root (in a separate data source) to do such things.
In theory, it could be like you suggest (similar to what for instance
Suse configuration tools do, which allow to temporarily login as root
when needed), but this is hard to do in an abstract and generic way,
and as OOo is intended for a lot more databases than MySQL, we need an
abstract and generic way ...
Comment 5 marting 2003-03-24 17:56:10 UTC 
auch... 
I connect myself to MySQL as 'root', with all the privileges!
Comment 6 Frank Schönheit 2003-03-26 12:46:28 UTC 
hmm, it seems I did not make myself clear :)

> I connect myself to MySQL as 'root', with all the privileges!

the problem is that though you do have all privileges, MySQL doesn't
tell us the proper privs.

Besides this, I mixed up things a little bit, sorry: when it comes to
editing columns, it's not about privileges, but about capabilities:
the driver does tell us that it's not _able_ to alter columns after
they have been created, and OOo simply respects this. The problem is
that the driver is lying :)

So even temporarily logging in as another user wouldn't help much, as
the driver would keep lying. The only possibility on OOo's side would
be to ignore what the driver tells ...
Comment 7 marting 2003-03-27 10:45:14 UTC 
by the way...
all the problem is the driver [MySQL ODBC 3.51] ?

mmm...
is a feature or bug in this driver?
:-/
Comment 8 Frank Schönheit 2003-05-20 11:40:41 UTC 
closing
Comment 9 hans_werner67 2004-02-02 12:52:28 UTC 
change subcomponent to 'none'