This is done on purpose and it is should not be corrupting the database. About date/datetime. All database (as far as I know) take datetime in input as a iso string. In fact if you were to pass a datatime object it would be converted to a datetime object. sqlite is special because not only takes is as a string, it also always stores it as a string.
I am not aware of any problem with the current implementation. If you think there is a problem, please post an example. It is possible I may be missing something. About other types. Validation is not done because validation is done at the level of forms already. If you need validation at the db level you can call db.table.validate_and_insert(....). Massimo On Thursday, 25 July 2013 12:56:45 UTC-5, David Ripplinger wrote: > > Currently, the DAL insert() function allows one to insert a record with a > DATE field containing a string type using sqlite as the database. My guess > is that there are other types that also go unchecked within the insert() > function. I think it would be a good idea to raise an exception or > something within insert() whenever the wrong type is passed into an > argument so that there is one less way of accidentally corrupting the > database. -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
