Hi,
Driver is almost complete. Please note the following:
- Autocommit mode is enabled by default works. Multi-statement
transactions don't work well yet.
- Long/blob and Unicode 'national character set' column types not
supported yet, but all other Ingres types are supported including
On 12-Feb-07, at 3:38 AM, Markus Hoenicka wrote:
Toby Thain [EMAIL PROTECTED] was heard to say:
I wish Sourceforge would deprecate tarballs entirely and just use Svn
tags. It seems (from another project I'm on, at least) that the
tarball is always woefully out of date.
My advice - go
On 15-Jan-08, at 12:58 PM, João Henrique Freitas wrote:
Hello,
Has libdbi some function to escape a string? Like PQescapeStringConn
(http://www.postgresql.org/docs/current/interactive/libpq-exec.html).
Have you checked the libdbi manual?
--Toby
I use dbi_conn_quote_string_copy, but it
On 13-Oct-08, at 7:15 AM, Markus Hoenicka wrote:
Hi,
just to clarify: it is sqlite, not the sqlite driver which does not
support newlines in SQL statements.
Wow, that's inconvenient. I imagine that must break very many ORM/SQL
generating layers.
--Toby
Some other SQL engines like MySQL
On 19-Nov-08, at 8:42 AM, Ken Ramsay wrote:
Thanks guys,
MySQL defines the field as a DATETIME , so the return type is time_t.
No; you are using an expression, not the column, so the result type
is indeed BIGINT, as Markus surmised (his explanation was correct, as
far as I can
On 18-Jan-10, at 3:47 AM, Markus Hoenicka wrote:
Toby Thain t...@telegraphics.com.au was heard to say:
This is probably driver dependent. IMHO the first check would be to
see if the unexpected reversion to binary type is occurring within
libdbi or in libmysqlclient (or mysqld).
I bet
On 22-Jan-10, at 9:19 PM, Vikram Noel Ambrose wrote:
Markus Hoenicka wrote:
The older versions (dbi_initialize, dbi_conn_new and dbi_shutdown)
are
now implemented on top of these functions, using a single static
instance
handle.
Then why should those functions be deprecated? I'm
On 25/01/13 7:40 PM, markus.hoeni...@mhoenicka.de wrote:
Markus Hoenicka writes:
Another possible reason for problems is the table type. If someone
uses MyISAM tables, the result I got would be expected. However, MySQL
uses InnoDB tables as default these days, and I double-checked
On 26/01/13 8:30 PM, markus.hoeni...@mhoenicka.de wrote:
Toby Thain writes:
Yes, you just found out the hard way that it's wise to include ENGINE
specifications in MySQL CREATE TABLE's.
True indeed.
Actually I think the news is even worse: I seem to recall that MySQL can
even