This problem is still in 2.14.4. This use case suggests the problem is
within form handling, nothing to do with database or adapter.
David Manns
On Monday, April 11, 2016 at 10:06:41 AM UTC-4, David Manns wrote:
>
> There is a similar problem with SQLFORM.factory. E.g:
>
> searchform=SQLFORM.factory(
> Field('name', 'string', default='', comment='(start of) last
> name'),
> Field('status', 'string', requires=IS_EMPTY_OR(IS_IN_SET(['Full',
> 'Student', 'Comp', 'Inactive']))),
> Field('paid_year', 'integer', requires=IS_EMPTY_OR(IS_PAID_YEAR()),
> comment="'yyyy' or '0', paid date 9/30/'yyyy'
> or no paid date"),
> ...)
>
> if searchform.accepts(request.vars, session):
> session.membersearch=searchform.vars
> ....
>
> In searchform.vars the default empty strings are represented as None
> rather than as empty strings.
>
> On Thursday, March 31, 2016 at 10:39:23 PM UTC-4, Raul Monares wrote:
>>
>> Hello
>> I just updated to version 2.14.3 and noticed that empty strings are being
>> stored as null in database field. This didn't happened in 2.13.4.
>>
>> Is this the intended behavior ?
>>
>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
