-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Dienstag, 30. September 2008 13:29
To: dev@dba.openoffice.org
Hi Frank,
If you want, we can create a CWS based on this milestone, and commit
your changes (or you can do yourself, if you want, after we
Hi Michael,
Okay, I went through some documents introducing to the CWS concept. In
case using a CWS to apply my changes, I'll need to checkout the most
recent milestone via cwsquery, create the CWS via cwscreate, apply my
changes locally to the CWS and commit them to the CWS via a CVS commit,
Hello Frank and Ocke,
It's been a while since I wrote to the mailing list last time, because I
was on vacation. You may remember that we were working on a driver. We
are finished with the driver so far and would like to integrate it into
the core code base. Probably we need to do some small
Hi Michael,
It's been a while since I wrote to the mailing list last time, because I
was on vacation. You may remember that we were working on a driver. We
are finished with the driver so far and would like to integrate it into
the core code base. Probably we need to do some small changes to
Hi Ocke,
I'm back :-)
That's great news, at least me ;-) Hope you had a good vacation.
First of all I have to clarify that default values which you enter
in the table design window are never propagated to the driver.
These default values are only UI values which will be shown when
you open
Hi Micha,
Michael Strobel wrote:
Hi Ocke,
I'm back :-)
That's great news, at least me ;-) Hope you had a good vacation.
Yes, Indeed I became a father. So less sleep. :-)
First of all I have to clarify that default values which you enter
in the table design window are never
Hi Michael Strobel wrote:
There is no issue for this, because I wanted to get sure that this is
problem is not related to our driver. Since I couldn't reproduce the
behavior with MySQL today, but only with Ingres I'm not quite sure about
that. On the one hand the default values are not saved
Hi Frank,
Hmm - you couldn't reproduce the default values vanishing, or you
couldn't reproduce the default values not being passed to the driver?
I couldn't reproduce the vanishing. The defaults were saved correctly
when connecting via the SDBC-JDBC bridge to MySQL or via OOo's MySQL
driver.
Hi Michael,
I'm still confused what is happening to the default values in Base. You
mentioned before that they never appear in the database and are stored
in the base document instead. Seems to be correct, they do never appear
in the database, but how is that done?
IIRC (it's a while since I
Hi Frank,
small misunderstanding - supplying the default from within the driver
is exactly the item which we don't have an infrastructure for. We can
easily add a setting to database documents, default it so that the
current behavior is unchanged - but then everybody creating an .odb
for
Hi Michael,
A flag saved at the data source / database document and supplying it's
default from within the driver is absolutely sufficient for our needs.
:-)
small misunderstanding - supplying the default from within the driver is
exactly the item which we don't have an infrastructure for. We
Hi Frank,
Nearly forgot that:
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
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
Hi Michael,
first of all thanks for your response. I think I forgot to tell this,
as I'm usuallyworking from Monday to Wednesday or Thursday only,
it may take some time till I respond to the mails here.
As you might have noticed, my answers are delayed, too - I do not work
on Fridays, and
Hi Michael,
Ocke's on vacation for a while, so let me jump in here.
Which classes you are talking about? The best way is to get rid of the
dependency of JDBC.
I need a specialized ResultSetMetaData class for the driver, but to
integrate this class I also need to inherit the Driver,
Hi Michael,
me again ;) Probably there is bug regarding the save process in Base
when changing a default value or a description text. It appears with
MySQL and Ingres, but not with HSQLDB. I reviewed the driver method
OTable::alterColumnByName, but I didn't find the root cause for this.
To
Hi Frank,
first of all thanks for your response. I think I forgot to tell this,
as I'm usuallyworking from Monday to Wednesday or Thursday only,
it may take some time till I respond to the mails here.
Now towards the weird driver architecture. You are right, my driver
does not inherit from the
Hi Frank,
One thing to mention is that the description text and the default
value, as you see them in the UI, might not be what you expect them
to be.
That is, those values are completely client-side at the moment, even
if the underlying database would support them, to. So, whatever you
Hi Ocke,
Which classes you are talking about? The best way is to get rid of the
dependency of JDBC.
I need a specialized ResultSetMetaData class for the driver, but to
integrate this class I also need to inherit the Driver, Connection,
PreparedStatement and ResulSet classes to make sure that
Hi Ocke,
me again ;) Probably there is bug regarding the save process in Base
when changing a default value or a description text. It appears with
MySQL and Ingres, but not with HSQLDB. I reviewed the driver method
OTable::alterColumnByName, but I didn't find the root cause for this.
To
Hi Micha,
Michael Strobel wrote:
Hi Ocke,
- how about just call dropObject at the views
Calling dropObject at the views results in a SQL exception since the
view is already dropped in the database. I just tried to catch the
exception and ignore it to see what happens, but calling
Moin Micha,
Michael Strobel wrote:
Hi Ocke,
I have created issues for the stuff, which we discussed last time I
posted here. It seems like it will still take a while until they are
treated. There are still a few more problems with the driver and hope
you have an idea how to solve this one:
A
Hi Ocke,
I have created issues for the stuff, which we discussed last time I
posted here. It seems like it will still take a while until they are
treated. There are still a few more problems with the driver and hope
you have an idea how to solve this one:
A view that references a table is
Moin Micha,
Michael Strobel wrote:
Hi Ocke,
You also have to check getColums, getPrimaryKey, getExportedKeys and
all occurrences where a table or column name can be asked for.
The best way is to look at the databasemetedata where a resultset is
returned.
Works. Only the table name
Hi Ocke,
You also have to check getColums, getPrimaryKey, getExportedKeys and
all occurrences where a table or column name can be asked for.
The best way is to look at the databasemetedata where a resultset is
returned.
Works. Only the table name that is displayed the tree view in the OO
Hi Ocke,
I didn't get the chance to finish the case sensitivity problem with Ingres yet,
but meanwhile I have discovered other things and probably at least one of them
is worth an issue.
For some reason Base can't handle values in long varchar columns that exceed a
length of 65535 characters,
Hi Ocke,
After save the table we ask the db metadata with getTabes and the
parameter filled for the table we saved. May be that doesn't return no
information. When you do a refresh it is mostly like creating a new
connection.
Thanks, that helped, at least a bit. The problem results from the
Hi Micha,
Michael Strobel wrote:
Hi Ocke,
After save the table we ask the db metadata with getTabes and the
parameter filled for the table we saved. May be that doesn't return no
information. When you do a refresh it is mostly like creating a new
connection.
Thanks, that helped, at
Hi Ocke,
That would be great. But an issue where you attach the bugdoc would
even be better :-)
I got the following mail from our JDBC driver developer, which makes me
think it's not an issue. What do you think?
--- snip ---
Working with LOB columns is extremely difficult due to many
Moin Micha,
Michael Strobel wrote:
Hi Ocke,
That would be great. But an issue where you attach the bugdoc would
even be better :-)
I got the following mail from our JDBC driver developer, which makes me
think it's not an issue. What do you think?
--- snip ---
Working with LOB
Hi Ocke,
You may have a look at connectivity/source/commontools/FValue.cxx.
This class is used to fetch the values from the result set and
dbtools.cxx as well.
How does your table structure look like? Could you create another db
(may be hsqldb) for a testing purpose with some sample data so
Hi MIcha,
Michael Strobel wrote:
Hi Ocke,
You may have a look at connectivity/source/commontools/FValue.cxx.
This class is used to fetch the values from the result set and
dbtools.cxx as well.
How does your table structure look like? Could you create another db
(may be hsqldb) for a
Moin Micha,
Michael Strobel wrote:
Hi Ocke,
Your patch work's fine with the test programs, but I'm still unable to
read and write long varchar columns in OO Base. I guess OO Base may be
mislead by our JDBC driver, which unfortunately returns always 0 for the
length and precision of long
No, the length and precision are only used when you try to change the
table layout or to create a new table.
The problem here seems to be that the data could not be read. The
method getString should always return something.
So may be calling getString for a long var char column doesn't work
Hi Ocke,
Your patch work's fine with the test programs, but I'm still unable to
read and write long varchar columns in OO Base. I guess OO Base may be
mislead by our JDBC driver, which unfortunately returns always 0 for the
length and precision of long varchar columns.
Methods that return always
Moin Ocke,
XClob is not well tested in OOo. Which type does your column have? May
be getCharacterStream works as well. Please submit an issue for the
XClob. Thank you.
The column type is long varchar. Using the the test programs - a JavaApp
and a OOoClientApp - mentioned in the last mail for
XClob is not well tested in OOo. Which type does your column have?
May be getCharacterStream works as well. Please submit an issue for
the XClob. Thank you.
Ahh, sorry, I didn't notice getCharacterStream. That explains how OOo
Base could retrieve the data from a MySQL database.
Hmm, no
Moin Micha,
Michael Strobel wrote:
Moin Ocke,
When you call at the metadata the getTypeInfo method which results do
you get? You could for example use the code in the qa folder as
template.
I wrote a small test program that calls getTypeInfo and shows the
result. Used NetBeans for
Moin Ocke,
What do you want to achieve with the TypeDescriptionInfo? May be your
Double type doesn't need any parameters, just a guess.
You have an own JDBC driver? Then change the getTypeInfo there :-)
Right, the Ingres double type doesn't expect any parameters. It's
definitely a bug in
The rename entry is already there. I would take the sources from the
mysql driver and change the sql statement in such way that ingres
understand it :-)
It has been quite a while and there is still more refinement needed,
but finally the driver compiles and the basic stuff works :-)
Moin Michael,
Michael Strobel wrote:
Moin Ocke,
thanks for your fast reply :-)
Normally I attach the debugger to the process or start soffice.bin
directly. But it depends on your operating system ;-)
Okay, make debug seems to be sufficient to create the symbols for the
debugger :-)
Hi Michael,
Michael Strobel escribió:
Hi,
I try to develop a SDBC driver for Ingres and OOo
Could you give me some advice how to manage this problem, please? Do I need to compile the whole OOo source code, besides using the OOo SDK or should I try something totally different?
sure Frank
Hi,
The only C++ external UNO driver component I know is the PostgreSQL
SDBC
driver, but this component is not a true independent extension, as
it
is (AFAIK) build linking against the connectivity module libraries.
the postgresql driver is an implementation, that just links to ODK
Hi Joerg,
Joerg Budischewski escribió:
Hi,
The only C++ external UNO driver component I know is the PostgreSQL
SDBC
driver, but this component is not a true independent extension, as
it
is (AFAIK) build linking against the connectivity module libraries.
the postgresql driver is an
Hi Ariel,
(answering the easy questions first, sorry Michael, your questions are
more time-consuming to answer)
* do you have any idea if external drivers linking against connectivity
libs. will break in the 3-layer OOo?
Joerg already pointed out that the PostgreSQL driver in fact is what
45 matches
Mail list logo