Of cours you can change you db manually with SQL DLL... You can still adjust your web2py model and do fake_migrate=True, migrate=False to get thing in sync...
Richard On Wed, Jan 22, 2014 at 1:13 PM, User <[email protected]> wrote: > I also would like a non-null foreign key reference, but like OP > experienced web2py will not create one. Why is this? And is there a > workaround to make reference fields not null? Or worst case can I add the > not null constraint manually in the db without breaking anything? > > > On Tuesday, June 19, 2012 11:40:37 AM UTC-4, Ivan wrote: > >> Same problem here! >> The "notnull=True" parameter doesn't append the "NOT NULL" clause for >> reference fields. >> The IS_IN_DB function activates the check at form-level while the notnull >> parameter should set the constraint at db-level. >> >> -- > 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/groups/opt_out. > -- 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/groups/opt_out.
