Your message dated Fri, 24 Aug 2007 23:53:10 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Processed: reassign 434067 to libmyodbc
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: libodbc-ruby1.8
Version: 0.9993-1
Severity: important
Hello,
thank you for maintaining libodbc-ruby1.8.
I wanted to deploy some code of mine on an etch system and it failed
miserably. I've managed to reliably reproduce the problem on my amd64
server with the following script:
#!/usr/bin/ruby
require 'odbc'
require 'csv'
$dsn = ARGV.shift
$uid = ARGV.shift
$pwd = ARGV.shift
@conn = ODBC.connect($dsn, $uid, $pwd)
begin
@conn.do("DROP TABLE test")
rescue
# Ignore errors on DROP TABLE
end
@conn.do("CREATE TABLE test ( id SMALLINT PRIMARY KEY );")
begin
newtest = @conn.proc("INSERT INTO test (id) VALUES (?)") { |stmt|
stmt.nrows }
newtest.call(1)
newtest.call(2)
newtest.call(3)
select = @conn.prepare("SELECT id FROM test")
select.execute.each { |row| puts row }
ensure
newtest.statement.drop
end
If I enable logging in MySQL, these are the queries that I get:
DROP TABLE test
CREATE TABLE test ( id SMALLINT PRIMARY KEY )
INSERT INTO test (id) VALUES ('7734156594425888769')
INSERT INTO test (id) VALUES ('2')
INSERT INTO test (id) VALUES ('651089476973494275')
Best regards,
Enrico
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-amd64
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Versions of packages libodbc-ruby1.8 depends on:
ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries
ii libiodbc2 3.52.4-5 iODBC Driver Manager
ii libruby1.8 1.8.5-4 Libraries necessary to run Ruby 1.
libodbc-ruby1.8 recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 3.51.15r409-1
> With libmyodbc 3.51.11-6.1 (etch) and MySQL 5.0.45-Debian_1-log (testing)
> on my box (amd64, 64 bits), the inserting '1' became '32767'. While, there
> was no problem with libmyodbc 3.51.15r409-1+b1 (testing). They were tested
> with both libodbc-ruby1.8 0.9993 (etch) and 0.9995 (testing).
> It seems to be an issue of libmyodbc as you reported[1].
> Taking a look at the upstream's changelog, some 64-bit issues were fixed
> at 3.51.14. Probably, this:
> * Connector/ODBC may insert the wrong parameter values when using prepared
> statements under 64-bit Linux. (Bug #22446)
Well, if this is a libmyodbc bug (which I'm not sure of, libodbc-ruby is
the only place that the bug manifests in my tests), then it's fixed in the
current version in testing. So closing the report...
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
--- End Message ---
