https://bugs.freedesktop.org/show_bug.cgi?id=68426
--- Comment #14 from Alex Thurgood ipla...@yahoo.co.uk ---
(In reply to comment #13)
sarcasam on Fantastic ! sarcasm off
Will try messing around with the collation and charsets.
I now recall getting bitten by a similar problem with OOo2.1 on
https://bugs.freedesktop.org/show_bug.cgi?id=68426
--- Comment #15 from Alex Thurgood ipla...@yahoo.co.uk ---
Result ! yes, thanks Lionel.
It seems that it is sufficient to just set the charset in the odbc.ini file,
however I have done as you suggested and set both to the same value in odbc.ini
https://bugs.freedesktop.org/show_bug.cgi?id=68426
--- Comment #12 from Lionel Elie Mamane lio...@mamane.lu ---
It looks like the table name is given in UTF-16, but that is not the encoding
that MySQL expects.
It works for me on Debian GNU/Linux amd64 (64 bits). However, I can reproduce
https://bugs.freedesktop.org/show_bug.cgi?id=68426
Lionel Elie Mamane lio...@mamane.lu changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=68426
--- Comment #11 from Lionel Elie Mamane lio...@mamane.lu ---
What bugzilla does not like is the NULL characters in the SQL command, in the
schema and table name... which are also most probably the reason for this bug.
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=68426
--- Comment #10 from Alex Thurgood ipla...@yahoo.co.uk ---
Created attachment 84636
-- https://bugs.freedesktop.org/attachment.cgi?id=84636action=edit
text of full error messages
Output of error messages when attempting to display the contents
https://bugs.freedesktop.org/show_bug.cgi?id=68426
Alex Thurgood ipla...@yahoo.co.uk changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
https://bugs.freedesktop.org/show_bug.cgi?id=68426
Alex Thurgood ipla...@yahoo.co.uk changed:
What|Removed |Added
CC||lio...@mamane.lu
---
https://bugs.freedesktop.org/show_bug.cgi?id=68426
--- Comment #7 from Alex Thurgood ipla...@yahoo.co.uk ---
Sigh...if that's the case, then we're in trouble when it comes to reporting SQL
problems on Base. Is this some recent BZ SQL injection clean-up zeal or
something ? There never used to be a
https://bugs.freedesktop.org/show_bug.cgi?id=68426
--- Comment #1 from Alex Thurgood ipla...@yahoo.co.uk ---
Strange, my report got chomped, so reposting :
With my shiny new 64bit OSX build of LO master :
Version: 4.2.0.0.alpha0+
Build ID: 22d1beb78a475e4846af945afde1c4d6c263b5d6
I can connect
https://bugs.freedesktop.org/show_bug.cgi?id=68426
--- Comment #2 from Alex Thurgood ipla...@yahoo.co.uk ---
With my shiny new 64bit OSX build of LO master :
Version: 4.2.0.0.alpha0+
Build ID: 22d1beb78a475e4846af945afde1c4d6c263b5d6
I can connect to a registered ODBC datasource, and see the
https://bugs.freedesktop.org/show_bug.cgi?id=68426
--- Comment #3 from Alex Thurgood ipla...@yahoo.co.uk ---
With my shiny new 64bit OSX build of LO master :
Version: 4.2.0.0.alpha0+
Build ID: 22d1beb78a475e4846af945afde1c4d6c263b5d6
I can connect to a registered ODBC datasource, and see the
https://bugs.freedesktop.org/show_bug.cgi?id=68426
--- Comment #4 from Alex Thurgood ipla...@yahoo.co.uk ---
With my shiny new 64bit OSX build of LO master :
Version: 4.2.0.0.alpha0+
Build ID: 22d1beb78a475e4846af945afde1c4d6c263b5d6
I can connect to a registered ODBC datasource, and see the
https://bugs.freedesktop.org/show_bug.cgi?id=68426
Alex Thurgood ipla...@yahoo.co.uk changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=68426
Qubit qu...@runcibility.com changed:
What|Removed |Added
CC||qu...@runcibility.com
---
15 matches
Mail list logo
