Widgets (even custom ones) are quite easy: translating what list:string is at the database level is another matter entirely. IMHO in this case there's more "lack of HTML wizardry" rather than "lack of database backend features"... If I understood what you're calling "what django admin does", be aware that it doesn't do anything like list:string does (which is accomodating n inputs in a single column, enriching it with "list" features) rather it links transparently a one-to-many relationship where n inputs are translated to multiple rows with a reference to the "parent" record. If what you're trying to achieve is a "select or add" widget, you'd be better off with a child table. Also, a big problem arises: as long as you want to add urls, it's just strings, and you could be happy with list:string. The real big deal is multiple file inputs: you can't really think of a good method to store multiple files referenced by a single record...
<tl;dr> nobody invented it, code your own, and use a child table to avoid headaches. On Monday, May 2, 2016 at 10:18:47 PM UTC+2, Ron Chatterjee wrote: > > > You making the feature request? lol > > On Sunday, May 1, 2016 at 12:01:31 PM UTC-4, Niphlod wrote: >> >> the answer is pretty easy....there is no list:datetime Field type. >> >> On Friday, April 29, 2016 at 3:58:48 PM UTC+2, [email protected] >> wrote: >>> >>> works: >>> Field("something", 'list:string'), >>> Field("someting2", 'list:integer'), >>> >>> But no such thing as: >>> Field("something3", 'list:datetime') >>> >>> I imagine its same as upload field, we need to create a one to many >>> relationships with a table. Any shortcuts? >>> >>> >>> >>> On Tuesday, January 19, 2016 at 2:47:44 AM UTC-5, Manuele wrote: >>>> >>>> Il 19/01/16 03:17, 黄祥 ha scritto: >>>> >>>> just wondering why the requires list in a list type [] is not work >>>> properly when update (when insert goes fine): >>>> e.g. >>>> table.email.requires = IS_LIST_OF([IS_LOWER(), IS_EMAIL(), >>>> *IS_NOT_IN_DB(db, >>>> table.email)* ] ) >>>> >>>> In case of update I think you have to change the validator logic >>>> because email uniqueness is no more requested or in case you update using >>>> a >>>> form maybe the detect_record_change[1] can help you. >>>> >>>> Cheers >>>> >>>> M. >>>> >>>> [1] >>>> http://web2py.com/books/default/chapter/29/07/forms-and-validators#Detect-record-change >>>> >>>> >>>> the problem when update is validator IS_NOT_IN_DB() is always true >>>> Value already in database or empty >>>> >>>> any idea how to face this? >>>> >>>> thanks and best regards, >>>> stifan >>>> -- >>>> 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. >>>> >>>> >>>> -- 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.
