It seems this bug is still present in 2.9.5
Il giorno venerdì 24 gennaio 2014 03:19:05 UTC+1, User ha scritto: > > Thanks. Here is the issue in case anyone is interested: > > http://code.google.com/p/web2py/issues/detail?id=1395 > > > On Wednesday, January 22, 2014 3:39:56 PM UTC-5, Anthony wrote: > >> This is a bug, and an issue has been created. Yes, you should be able to >> make the change directly in the database. >> >> Anthony >> >> On Wednesday, January 22, 2014 1:13:30 PM UTC-5, User wrote: >>> >>> I also would like a non-null foreign key reference, but like OP >>> experienced web2py will not create one (I'm using postgresql). 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
