[web2py] Re: Tag handling suggestions

2011-10-11 Thread stefaan
How does choosing option 1 <--> option 3 affect building a UI ? It seems to me that option 1 can be used "as-is" in an SQLFORM.grid containing other fields, whereas option 3 might require a separate SQLFORM.grid to manage the correspondence tags<->items? If this is just me not understanding all p

Re: [web2py] Re: Tag handling suggestions

2011-10-11 Thread Martín Mulone
In my opinion I'll discard option number 1 if you are not running on GAE. Because is not a true SQL, is quite awfull indeed, bring it by nosql gae. But it's all depends on the amount of records. 2011/10/10 Bruno Rocha > I like this, and it is really smarter than list:string option, but, imagine

Re: [web2py] Re: Tag handling suggestions

2011-10-10 Thread Bruno Rocha
I like this, and it is really smarter than list:string option, but, imagine a blog where users include tags in an INPUT text field, this will be more difficult to store tags in other table (you can do using ajax or building a checkbox list of tags) but it is easy just to let the user put tags in a

[web2py] Re: Tag handling suggestions

2011-10-10 Thread Massimo Di Pierro
I think Option 1 if faster on GAE Datastore. Option 3 is the best on SQL because you can do db.define_table('data', Field('value')) db.define_table('tag', Field('record_id', db.data), Field('name')) def search_or(data=db.data, tag=db.tag, tags=[]): rows = db(data.id==tag.record_id)\