Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

Re: [tdf-discuss] Re: A failed query to ODBC data source


Thank you, Alex.

You have evidently paid quite some attention to my question.
Does this mean that you think the issue is worth following
up on?

For comparison, the competitor for my attention (and the
thing that got me into this mess) is bug 34309 "Error on
importing a timestamp field from db2 via ODBC"
<https://bugs.freedesktop.org/show_bug.cgi?id=34309>.


On Wed, 2011-08-17 at 19:13 +0200, Alexander Thurgood wrote:
Le 17/08/11 16:30, Terrence Enger a écrit :

Hi Terry,
[snip]

Is your field perchance being flagged as an <OBJECT> ? 

It should not be.  The field is "KEYFIELD" in table AA6411
described in bug 34309 "Error on importing a timestamp field
from db2 fia ODBC"
<https://bugs.freedesktop.org/show_bug.cgi?id=34309>.  The
field specification is

      keyfield     int        not null   primary key,

[snip]
                                                        However, I do
remember there previously being problems with DB2 ODBC drivers.

Well, OO.o bug 110236 "Error: operator delete mismatch"
<http://openoffice.org/bugzilla/show_bug.cgi?id=110236>
jumps to mind because I am still seeing those assertions
raised.  (I am user "400guy" on that bug tracker.)

Beside the fact that my field is a common garden-variety
integer, I have to think that the ODBC driver works in at
least some contexts because LibreOffice received with
ubuntu-natty, which identifies itself as

    LibreOffice 3.3.3 
    OOO330m19 (Build:301)
    tag libreoffice-3.3.3.1, Ubuntu package 1:3.3.3-1ubuntu2

can query the table without difficulty.

[snip]
Have you searched to see if anything is in the old OOo dba mailing list
archives on this topic ? 

I am subscribed to that (now very quiet) list.  I think I
would have noticed a reference to db2/i.

(But let's see what google can find.  ...  Okay, I'm back.)

[ db2 "The data content could not be loaded."
  site:openoffice.org
] returns 57 hits.  This would be a place to start, if the
issue is worth considering.  That, of course, is my
underlying question.

                         I suppose you could always try canvassing
someone from IBM over at the Apache-OOo project, but they might just
tell you to use the JDBC driver instead.

Well, it was a bug report that got me into this, not a real
need to use db2 from LibreOffice.  So I think it a good idea
not to spread my attention to JDBC.

However, I catch the implication that IBMers hang out over
there.  Maybe somebody could agitate there for a fix to the
operator delete mismatch in the ODBC driver.  Does
LibreOffice have a "minister of external affairs", so to
speak?

I think the first step toward such an approach should be a
new bug report on which I can hang stack backtraces and so
forth, right?  OTOH, I hesitate to clutter up the bug
tracker when OO.o already resolved the problem INVALID.


I don't think there are many db2 users on this list, or even on the
users list.

Yes, <whine>I feel lonely</whine>.


On Wed, 2011-08-17 at 19:19 +0200, Alexander Thurgood wrote:
[snip]
I had a trawl in my old dba messages, and found a reference to a problem
where OOo did not respect the Concurrency and SCROLL_SENSITIVITY
settings that were being passed by the driver from the DB server
connection. Perhaps this is where your problem lies ?

http://www.mail-archive.com/dba-cvs@openoffice.org/msg00858.html

Well, I do not see a parameter to adjust that in my data
source configuration.  Does that mean that LibreOffice is
setting the (connection?) attributes on its own?  Is there a
reason why these should have changed since ubuntu-natty?

This i just a long way to say "I dunno".


On Wed, 2011-08-17 at 19:22 +0200, Alexander Thurgood wrote:
Le 17/08/11 16:30, Terrence Enger a écrit :


Possibly a wild goose chase, but I also found this :

http://openoffice.2283327.n4.nabble.com/ResultSetType-Settings-in-Openoffice-Base-td2783193.html

My case is different in that the failing query can be as
simple as "select * from AA6411".

Still, this is a good reminder that macro coding is
available for exploring attributes that the GUI does not
make manifest.


Thanks,
Terry.



-- 
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.