You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the metaType 'X', which represents blob fields in all other databases, is mapped to a varchar(250) field in the sqlite3 driver. Whilst the flexible typing in the sqlite database means that this is not necessarily an issue , I believe for consistency with other databases, It should map to a blob field.
The text was updated successfully, but these errors were encountered:
I think we need to use an sqlite specific metaType function with the correct type mapping and leave the default one pointing to varchar which is pretty generic, as there is a bit of difference in the names of text fields across databases.
Sqlite datahases have very limited datatypes. The metaType
function defaults to the standard version which is based on
the mysql standards. The new driver specific version provides
a metatype mapping based on the sqlite datatype affinities
Sqlite datahases have very limited datatypes. The metaType
function defaults to the standard version which is based on
the mysql standards. The new driver specific version provides
a metatype mapping based on the sqlite datatype affinities
dregad
changed the title
Should Sqlite map metaType X to a blob field instead of Varchar
Fix Sqlite metaType mappings (map X to Blob instead of Varchar)
Feb 4, 2016
Currently, the metaType 'X', which represents blob fields in all other databases, is mapped to a varchar(250) field in the sqlite3 driver. Whilst the flexible typing in the sqlite database means that this is not necessarily an issue , I believe for consistency with other databases, It should map to a blob field.
The text was updated successfully, but these errors were encountered: