On 15 May 2019, at 2:37am, D Burgess <dburges...@gmail.com> wrote: > I have a SQLite database that was ported from mysql. Most of the > column definitions remain unchanged. > There is lots of CHAR and VARCHAR definitions and contrary to Simon's > response they mean what they say.
No problem with SELECTing an existing value. As I wrote, the difference comes when you try to store a new value. See <https://dev.mysql.com/doc/refman/5.7/en/char.html> In MySQL, supply 'ab' for CHAR(4) and it stores 'ab '. In SQLite, supply 'ab' for CHAR(4) and it stores 'ab'. In MySQL, supply 'abcde' for VARCHAR(4) and it stores 'abcd'. In SQLite, supply 'abcde' for VARCHAR(4) and it stores 'abcde'. I /think/ the above is true. I know more about SQLite than I do MySQL. Which isn't saying much. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
