Hello Michael,

> I would like to prevent that OOo Base asks if it should delete a column
> and append a new one, when the column definition can't be modified. Is
> it possible to do this from within the driver or switch it of in one of
> Base's option dialogs (I didn't see anything like this, but maybe I
> overlooked it)? There are two problems with this. First is that if the
> user has entered data into the column before the data is gone when the
> column is deleted and OOo Base shows no respective warning. Second is
> that in certain cases Ingres can't append a column to an existing table,
> for example if the column is not null and it has no default value. So I
> think it would be better to disable this feature when using Ingres.

If the problem would only be the missing warning, I'd vote for adding it
to the dialog which asks the user (which would be a Good Thing (TM),
anyway) ..

There's no mechanism in place to disable the feature. We can introduce
one, though I fear you have no time to wait for what I would consider
the cleanest solution ;-) (namely creating an infrastructure for drivers
to be deployed into OOo, together with a set of configuration-based
"meta-data" about the supported functionality of the driver).

Usually, disabling (or changing) a certain behavior is done by flags
saved at the data source / database document. Would this be sufficient
for you? I.e., everybody creating a new database document using your
driver would need to do this setting once. (And perhaps we can introduce
a mechanism to let the driver tell defaults for certain settings.)

Alternatively, it would be possible to let the driver in general tell
that a certain UI feature is disabled, but as said, there's no
infrastructure in place for this at all - we would need to respect both
the data source and the driver settings, where currently only data
source settings are respected.

Which brings me to the following question: What you do currently - is
this intended to be contributed back to the core code base? That is, if
you do changes to Base's code base outside your driver, then you would
either need to build an own OOo containing those changes, or contribute
them to the project for inclusion in the next release.

The feasibility of different solutions depends on how you want to handle
this.

Ciao
Frank

-- 
- Frank Schönheit, Software Engineer         [EMAIL PROTECTED] -
- Sun Microsystems                      http://www.sun.com/staroffice -
- OpenOffice.org Base                       http://dba.openoffice.org -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to