Skip Menu |
 

This queue is for tickets about the DBD-SQLite CPAN distribution.

Report information
The Basics
Id: 17218
Status: resolved
Priority: 0/
Queue: DBD-SQLite

People
Owner: Nobody in particular
Requestors: ptomblin [...] xcski.com
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 1.11
Fixed in: (no value)



Subject: Not respecting text fields
Download (untitled) / with headers
text/plain 532b
Using syntax that works in DBD::MySQL and DBD::PostgreSQL, I attempt to insert values into a varchar(10) field. But if the value is one that *could* be interpreted at a number, it is interpreted as a number first, and then inserted into the varchar(10) field. For instance $id = '0E9'; $wptInsertStmt = $conn->prepare(qq{ INSERT INTO waypoint (id) values(?)}); $wptInsertStmt->execute($id); is ending up with "0" in the database instead of "0E9". (DBD::SQLite 1.11 and perl v5.8.4 installed from Debian Sarge repository)
Download (untitled) / with headers
text/plain 709b
On Sun Jan 22 22:06:17 2006, guest wrote: Show quoted text
> Using syntax that works in DBD::MySQL and DBD::PostgreSQL, I attempt to > insert values into a varchar(10) field. But if the value is one that > *could* be interpreted at a number, it is interpreted as a number first, > and then inserted into the varchar(10) field. For instance > $id = '0E9'; > $wptInsertStmt = $conn->prepare(qq{ > INSERT INTO waypoint (id) values(?)}); > $wptInsertStmt->execute($id); > is ending up with "0" in the database instead of "0E9". > > (DBD::SQLite 1.11 and perl v5.8.4 installed from Debian Sarge repository)
Turns out I was testing with 1.08 (Debian Sarge) not 1.11. Installing from the 1.11 source fixed the problem.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.