> But http://sqlite.org/datatypes.html and > http://sqlite.org/datatype3.html says: > > "The search for these strings in the type declaration is case > insensitive, of course. If any of the above strings occur anywhere in > the type declaration, then the datatype of the column is text. Notice > that the type "VARCHAR" contains "CHAR" as a substring so it is > considered text." > > "If the datatype of the column contains any of the strings "CHAR", > "CLOB", or "TEXT" then that column has TEXT affinity. Notice that the > type VARCHAR contains the string "CHAR" and is thus assigned TEXT > affinity." > > I think the sqlite and sqlite3 drivers must treat CHAR as TEXT not > INTEGER (TINY). > > It's right?
I don't really think. This text explain how the data it's represented internally, inside the sqlite database file, not how it's presented to the user. In fact, the driver helps you, transforming that data to a numerical value, as you use it in your software. If it remains text, then you have to call atoi() on that field to get the numerical value. -- Claudiu Nicolaie CISMARU GNU GPG Key: http://claudiu.targujiu.net/key.gpg T: 0755135455 E: [EMAIL PROTECTED], [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________ libdbi-users mailing list libdbi-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libdbi-users
