Greetings,
As part of proposing a patch for a bug I filed (#12180), I ran across
this ticket, and took the liberty of claiming it. Since I'm
relatively new to working on Django code proper, I wanted to start a
discussion about possible approaches to solving these issues.
I see two basic philosophical approaches:
1. The "safety razor" approach: Django checks the version of the
database server software, and either adapts its functionality to it or
(at least) provides an early and explicit error, even at the cost of
some performance.
2. The "straight razor" approach: Django accepts any statements the
user code makes about the database software at face value, and
maximizes performance, accepting that the user being wrong will result
in an obscure error at some random point.
Some specific things I'd like to accomplish:
-- Allow Django to use the INSERT...RETURNING functionality of PG 8.2+
even if autocommit isn't being used.
-- Get rid of the need to repeatedly call SELECT version().
Some other functionality that's not directly relevant to this ticket,
but related and useful:
-- Allow for Serializable transactions.
Thoughts?
--
-- Christophe Pettus
x...@thebuild.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
