orking *around* django instead of with it.
Don't get me wrong, we love django and it is great for 75% of everything
out there but highly advanced database applications that require the
other 25% Django maks it a pain in the arse.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Comp
at the following:
http://www.modernmethod.com/sajax/
I would be curious as to all of your thoughts on its comparison to the
others mentioned above.
Joshua D. Drake
that has
to be a 1.0 rev type thing.
Joshua D. Drake
Maybe others have
grandiose plans for transaction support, but again, ISTM that's all we
really need. The developer gets to choose, and -- paradigmatically
speaking -- it's no different or less powerful than transaction usage
in
ociated
to multiple tables, I expect that if all the data is required within the
form , all the data
will make it into the database, or none will. Otherwise I end up with
inconsistent data which
is a big no no.
Sincerely,
Joshua D. Drake
Anybody have ideas on implementations? Let's
at all. If you don't want to use ACLs
you shouldn't have to.
Sincerely,
Joshua D. Drake
--
Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240
PostgreSQL Replication, Consulting, Custom Programming, 24x7 support
Managed Services, Shared and Dedi
think it is a maybe for django users/developers. If Django wants
to take off it is going to need some type of ACL otherwise people are
just going to develop their own and you will end up with a bunch of
different implementations.
Sincerely,
Joshua D. Drake
>
> Regards
>
> Laurent.
Hello,
Thought I would throw a bone out there and ask what it would take to get
transaction
support finished up?
Is there anything we can do to enhance the priority of the feature?
Sincerely,
Joshua D. Drake
--
Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240
