On Sun, Mar 29, 2015 at 4:57 PM, Russell Keith-Magee
wrote:
> It would probably be *possible* to refactor manage.py sqlall to use the new
> table creation logic; but the question would then be "why do you want it"?
Speaking from experience, I have found these commands to be a
extremely helpful wh
Ah, but the point I'm trying to make is that they're not two separate
notions at all.
The current migrations system was deliberately designed in a way such that
it is both - it's a representation of changes through time, sure, but it's
also an entire statement of how the database is made. Migratio
Hi Pascal,
On 03/30/2015 02:57 PM, Pascal Chambon wrote:
> Thanks for your answers,
>
> l'm confused nonetheless, because their are two notions mixing up, here,
> that we should probably separate:
>
> - the HISTORY of SQL schemas, aka "django/south migrations"
> - the CURRENT STATE of SQL schema
Thanks for your answers,
l'm confused nonetheless, because their are two notions mixing up, here,
that we should probably separate:
- the HISTORY of SQL schemas, aka "django/south migrations"
- the CURRENT STATE of SQL schemas, that I'll call "ORM Models Dump"
Let's leave the SQL data (and its m
On Thu, 26 Mar 2015 22:29:00 +0200
Shai Berger wrote:
> Hi Jani.
>
> On Wednesday 25 March 2015 09:58:00 Jani Tiainen wrote:
> >
> > We're still running Oracle and GIS. Though we do have built custom
> > backend based on Django GIS backend - mainly to have support for
> > Oracle XE, 3D function
