On Jun 13, 7:57 am, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > 1) /app/default/data defaults to /app/default/data/tables > > with select type links for each table. > > It is easy to do the same for create for example, where each link > > would be a create type link for the respective table, but is it a good > > idea?. > > Do not understand.
the idea was to have /app/default/data/create reply with a tables_with_create_links such as /app/default/data/create/xxx but you are against listing table names. > > > 2) /app/default/select creates a ticket while > > /app/default/data/select returns "404 not found" > > more consistent results would be better. > > I can fix this. > > > One fix would be to move the 'tables' default response into Crud.select > > (), but is it a good idea?. > > No because I do not expect people to exposed the full crud methods, in > pasrticular it may not be a good idea to list the table names. But then why list them with /app/default/data or /app/default/data/ tables? > > > 3) /app/default/data.xml (or json or...) is ignored while > > /app/default/data.xml/select/dog gives "invalid view" (no generic?) > > 4) Should Crud offer default serializers for xml, json, ... ? > > are you sure you have the lastet trunk and the latest scaffolding app? > these things shouldbe there. yes, if you mean I did: web2py.py -s app -u UPGRADE after downloading 1035. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
