19.3.2012 13:15, Andrew Godwin kirjoitti:
On 19/03/12 11:08, Jonathan French wrote:
On 18 March 2012 23:33, Russell Keith-Magee <russ...@keith-magee.com
<mailto:russ...@keith-magee.com>> wrote:
> 2. An inspection tool that generates the appropriate python code
after
> inspecting models and current state of database.
The current consensus is that this shouldn't be Django's domain --
at least, not in the first instance. It might be appropriate to
expose an API to extract the current model state in a Pythonic form,
but a fully-fledged, user accessible "tool".
I would, however, definitely recommend not touching the Oracle or MSSQL
backends - three is already a lot of work, and they're harder databases
to get a hold of for testing.
Here I would like to rise my concern - specially being long time Django
and Oracle user.. =)
First at all everyone can get hands on Oracle Express database, free of
charge standard Django stuff works in it very well. Geodjango doesn't
work with it. AFAIK MSSQL is something that is not officially supported
by Django so that shouldn't be much a problem if it's not touched.
Secondly Django has been in the past very consistent in support of four
databases: SQLite, PostgreSQL, MySQL and Oracle. All supported pretty
well as well as possible. I'm aware that doing migrations for all
databases is a time taking challenge to tackle around all peculiarities
in different backends. So hopefully that consistency is kept even with
new features like this.
And yes, second thing is of course Geodjango part which takes complexity
to whole new level.
--
Jani Tiainen
--
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.
