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.
>
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, C
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 reproduce
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 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 tha
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 that didn't
solve the actual problem.
> - or f
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 v
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 droppe
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 t
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 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 l
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 t
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 col
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 restr
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 testing
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
Hi Micha,
Michael Strobel wrote:
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
> 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 w
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 varchar
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
>> 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,
> 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.
Best regards
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 fo
Moin Micha,
Michael Strobel wrote:
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
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
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 th
> 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 :-)
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 :-) I'll keep trying to load the symbols in the MS
Moin Michael,
Michael Strobel wrote:
Hi,
the solution for the connection problem was rather simple, but hard to
find without the possibility to debug the component, the prefix
sdbc:ingres: is automatically added to the url string passed to the
connect() method and is not be entered in OOo. How
Hi,
the solution for the connection problem was rather simple, but hard to
find without the possibility to debug the component, the prefix
sdbc:ingres: is automatically added to the url string passed to the
connect() method and is not be entered in OOo. How do you debug
components compiled in the
Michael Strobel wrote:
Hi All, Moin Ocke,
first of all I like to thank you all for your efforts in helping and
supporting my attempts to write a driver and especially Ocke for
answering the questions concerning his code in-depth. It's great to see
the community here is that active and fast respo
Hi All, Moin Ocke,
first of all I like to thank you all for your efforts in helping and
supporting my attempts to write a driver and especially Ocke for
answering the questions concerning his code in-depth. It's great to see
the community here is that active and fast responding :-) Sorry, that I
w
Moin Michael,
first of all great to hear that you want to write a driver :-) I'll do
my best I can to help you at any time.
First of all you have to know which kind of driver you want. I just look
at the code and it looks promising to use either the ODBC or JDBC in the
independent way as wel
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 w
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
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
li
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.
And by reading Stephan Bergmann's mails (for example in
http://extensions.openoffi
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 wi
39 matches
Mail list logo
