I'm not quite sure what the second one does, could you explain it a bit
more?
for example right now I'm using it for testing. I have an app that depends a lot on the db, he URLs are taken from the contect in the db, something similar to what newsvine does. So I need data in the db for the app to work, since i'm still developing the model I find that I forgot something or that something needs to be added, so this way I can edit the data.sql.py file and then run it, it will drop all my tables create them again and add the test data, is much less type/typing then running tg-admin sql drop && tg-admin sql create, then having to run tg-admin shell and type in everything again, or click catwalk for everything again.
on the other hand it will be common for install, say you have an intranet app that needs to create the same set of users on each installation all you need to do is run that script.
Your fix for the self join is pretty neat. There is this
http://www.sqlobject.org/SQLObject.html#how-can-i-join-a-table-with-itself
in the SQLObject FAQ but I like your way of solving it with 2 keyword
arguments better
I'm not sure how the model for that fix will be created but certainly plain old simple sqlobject is better then messing with sqlbuilder. :)
The dummy template is a neat trick but but I'm not quite sure how I'd
use it unless you could call the dummy template via some synatic sugar,
ie (@expose("dummy")) or something like that. It might also be useful
for an error page.
as I said this is something that will probably will never get into a production app, it's just a way to forget about the template while coding the backend. the use i'm giving it now is that I have another project i'm working with a designer so we are deciding on the interface, i'm doing a test backend and he is doing a test frontend, the only way I can show him what I'm sending is with something like this. I'm using the same template to expose the following urls
/
/test
/users
/games
/players
/<dinamic created>
they all send out diferent types of data to the front end, lists, dicts, strings, SelectResults, all of them will eventually be replace with real templates but with dummy.kid I don't need to worry about them.
hope I clarify your isssues
Thanks for sharing with the rest of us!
sure np, TG has given me hopes that webprogramming is not doom :) seriously php and _javascript_s are 2 of the worst things that could had happen to the world.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/turbogears
-~----------~----~----~----~------~----~------~--~---
