On 4/27/06, Jonathan Ellis <[EMAIL PROTECTED]> wrote:
> It isn't SA's place to validate data for your database. If you want a
> database that's more rigorous about such things, then don't use sqlite. :)
But SA _is_ validating the data. The problem arises because SA is
validating it in the DB->Python direction, but not in the Python->DB
direction.
That's because validating what goes into the database is the database's job. Simple as that.
What _would_ be reasonable would be to expect SA to insert a
Python datetime object correctly, such that the reverse operation
happens as desired. (I haven't tested this on sqlite, but if it doesn't work it's a legitimate bug.)
But sqlite has always been agressively untyped; it's not SA's place to try to change that.
But sqlite has always been agressively untyped; it's not SA's place to try to change that.
--
Jonathan Ellis
http://spyced.blogspot.com
