Hi all,
Does anyone know if we're planning on adding the Java
class/function/method/whatever called getExportedKeys? (I'm not a Java
programmer).
I've been looking at the free Java product called DbVisualizer
(http://www.ideit.com/innovations/dbvis/), which can connect to a
database and create
On Thu, 30 Aug 2001 11:06:13 -0300, you wrote:
Thank you all for your help:
Dia Thursday, 30 de August, 2001 10:42, Rene Pijlman wrote:
like áéíóú (aeiou with accent)... they are replaced
by question marks (?)... any ideas?
What's the character encoding of the database?
It doesn't matter.
I'm forwarding this workaround to the list. Can someone shed
some light on this?
Java uses Unicode and should be able to represent all ISO
Latin-1 (8859-1) encoded characters. Why would we need to tell
the driver what character set the backend is sending us? Can't
it ask the backend dynamically?
On Thu, 30 Aug 2001 11:46:16 +0900, Thomas O'Dowd wrote:
I found some time this morning to write and test a new EscapeSQL()
method. I didn't make a patch for the driver yet as I'd like to
hear some comments.
To what extent is this implementation JDBC compliant?
The spec is in section 40.1.5
On Sat, Sep 01, 2001 at 11:02:47PM +0200, Rene Pijlman wrote:
On Thu, 30 Aug 2001 11:46:16 +0900, Thomas O'Dowd wrote:
I found some time this morning to write and test a new EscapeSQL()
method. I didn't make a patch for the driver yet as I'd like to
hear some comments.
To what extent is
On Mon, 27 Aug 2001 22:57:13 -0700, Barry Lind wrote:
I do not know what the server does if you have autocommit enabled
and you issue multiple statements in one try.
As you know, Peter Eisentraut said on hackers that all
statements in a semicolon-separated query string are processed
as one
* Rene Pijlman [EMAIL PROTECTED] wrote:
|
| Have you tried it with a database which was created with -E
| LATIN1 and with an installation configured with
| --enable-multibyte?
You don't need multibyte for iso-8859-1. A simple test case reproducing the
problem would be nice though. I don't have
