This identifies a single record: db.playlist.id<http://www.google.com/url?q=http%3A%2F%2Fdb.playlist.id&sa=D&sntz=1&usg=AFQjCNH5rdz7nysvc74JWdptNNjpq7AH7A> ==record.id
The point of this: db.playlist.playlist_title==record.playlist_title was to identify all record in the same playlist. I agreethat using playlist_title is not a good idea, perhaps you want to use a reference field to another table whete you keep the playlist titles. On Sunday, 19 January 2014 11:35:13 UTC-6, Jaime Sempere wrote: > > > Thanks a lot (and it was great adding support for several playlist), just > for future reference there is a small typo on db definition: > 'playlist_name' should be 'playlist_title' > > But I wanted to ask you... I would change the query: > > query = db.playlist.playlist_title==record.playlist_title > > for this > > query = > db.playlist.id<http://www.google.com/url?q=http%3A%2F%2Fdb.playlist.id&sa=D&sntz=1&usg=AFQjCNH5rdz7nysvc74JWdptNNjpq7AH7A> > ==record.id > > > Shouldn't this be a little more efficient? Is there any particular reason > for not re-writing like that? I guess in real cases there is no differences > on performance, but I just want to know that if could do that without any > side-effect. > > thanks again > > -- 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.
