-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/18/2011 02:20 AM, Stefan Keller wrote:
> for it kind of weak typing (meaning
> 'weak' compared to the information schema).
SQLite's typing is not weak. YOU GET BACK OUT WHAT YOU PUT IN. I'd argue
other implementations are the problem since they require that a particular
column only store one type meaning you are screwed if you need more than one.
Additionally you can use CHECK constraints to enforce whatever "information
schema" you want so you can trivially make it behave like other implementations.
> Weak typing in databases assigns the house keeping of consistency to
> the writer - who is often unknown in database uses cases.
SQLite is a library so it can only be used directly in a process on a local
file. I can't reach across the Internet and do unknown things to your database.
If your implementation requires particular constraints ("consistency" as you
call it) for any particular row or column then use a CHECK constraint which
will be enforced. It is that trivial and will affect anything else that
manipulates the database.
Roger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk2sdVIACgkQmOOfHg372QSqvACghtFobTBivNkiEm6BBJjc3mFC
aDsAoMGtyCLX5yTZ/E4++uwYha0XyzA1
=2egU
-----END PGP SIGNATURE-----
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
