>>> The type you probably want is TEXT. >> >> The rules are such that VARCHAR column also gets TEXT affinity. > > I thought it was worth explaining to him what was really going on. Didn't > want him going through 30 databases changing hundreds of fields to VARCHAR > when he should be changing them to TEXT.
If changing all fields either to TEXT or to VARCHAR has the same result then why bother? What's the difference? Pavel On Sat, Apr 21, 2012 at 12:08 PM, Simon Slavin <slav...@bigfraud.org> wrote: > > On 21 Apr 2012, at 5:03pm, Igor Tandetnik <itandet...@mvps.org> wrote: > >> Simon Slavin <slav...@bigfraud.org> wrote: >>> On 21 Apr 2012, at 2:04am, Braddock Gaskill <bradd...@braddock.com> wrote: >>> >>>> I now see that if I properly define the field type as VARCHAR instead of >>>> STRING that the CSV is correctly parsed. >>> >>> SQLite doesn't have either of those types. It's doing its best to guess >>> what you mean. Take a look at >>> >>> <http://www.sqlite.org/datatype3.html> >>> >>> The type you probably want is TEXT. >> >> The rules are such that VARCHAR column also gets TEXT affinity. > > I thought it was worth explaining to him what was really going on. Didn't > want him going through 30 databases changing hundreds of fields to VARCHAR > when he should be changing them to TEXT. > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
