Well, some more context then: I've worked at a company that have exactly the same logic writen in perl and using an ORM built inside the company. The ideia was to build a plataform to interact with the DB, and with this interaction, extend the information about the table been created/modified or the field been created/modified, and with that, build web views and forms dynamically from that extended schema. The business logic was entirely in database triggers, and javascript (one of the extensions of the fields information was that it was possible to write javascript events, and the plataform binded that event to the view). Needless to say, everithing was heavly cached: everytime the schema (or the extended schema) was updated, it was serialized and cached in a redis environment, so it was always ready to query.
It worked preaty well, and was a tool good to work with. So i thought: "well, i gess that can built with django!". And here I am. :) Any questions, I'm always aviable. Thanx! -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAOs3Lp4MfEysqWSA-pYMD_PRvDpByLjSKc27dcP%2BQq2Ra6tXRA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
