[prev] [thread] [next] [lurker] [Date index for 2005/05/25]
I know that at least one other member of our carthartic little bile cabal has come across this problem http://use.perl.org/~hex/journal/24191 but some combination of Class::DBI, DBI, DBD::SQLite and sqlite is fucking up my cabbage patch. I'm using SQLite for rapid prototyping and I want to stick a version into a DB. A version is a string because, well, apparently just having incrementing numbers is too difficult for people or something. Either way, this shouldn't be a problem. Right? Right? Just set the column type to VARCHAR. Or TEXT. Or BLOB. Or CLOB. Any of those? No. SQLite trys to promote whatever goes in to be a number. Despite claiming that it won't "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. If the datatype for a column contains the string "BLOB" or if no datatype is specified then the column has affinity NONE." http://www.sqlite.org/datatype3.html MY SCHEME DOES DEFINE IT AS ONE OF THOSE! YOU SYPHILLITIC PILE OF GYM SOCKS! In fact I've tried everyone of those and also the trick of manually and explicitly setting the data type to be BLOB. But no. Apparently the simple taks of sticking exactly what I want into the database is too difficult. I apparently misunderstood the point of a database - here I was thinking that it was store data and, in fact, it's intended purpose is TO MAKE MY LIFE A MISERY. *sigh*
Generated at 04:00 on 26 May 2005 by mariachi 0.52