Django logging database changes

2010-10-10 Thread David
Hello I have a very simple app that I am writing that simply stores form data to a database. I can then scroll through and edit data stored in the database. I was wondering if there is a built in function that would enable me to log all data update/changes like the django admin history log does.

Re: replicating database changes from one postgres DB to another

2009-07-23 Thread Steve Howell
On Jul 21, 3:18 pm, Wayne Koorts wrote: > Hi Steve, > > > We have an application where we periodically import data from an > > external vendor, and the process is mostly automated, but we need to > > review the data before having it go live. > > > We were considering an option where we would run

Re: replicating database changes from one postgres DB to another

2009-07-21 Thread Wayne Koorts
Hi Steve, > We have an application where we periodically import data from an > external vendor, and the process is mostly automated, but we need to > review the data before having it go live. > > We were considering an option where we would run processes on another > database, do the manual valid

replicating database changes from one postgres DB to another

2009-07-21 Thread Steve Howell
We have an application where we periodically import data from an external vendor, and the process is mostly automated, but we need to review the data before having it go live. We were considering an option where we would run processes on another database, do the manual validation, and then replic

Re: Database changes

2007-02-20 Thread Honza Král
On 2/20/07, Mike H <[EMAIL PROTECTED]> wrote: > > > For me, if there was a way to simply add missing columns that would be > enough. Any data manipulation should be done by a patch runner that can > be tested and automated, but simply adding missing columns to a table I > think should be done by sy

Re: Database changes

2007-02-20 Thread Mike H
For me, if there was a way to simply add missing columns that would be enough. Any data manipulation should be done by a patch runner that can be tested and automated, but simply adding missing columns to a table I think should be done by syncdb. The way I have approached this when producing ORM

Re: Database changes

2007-02-20 Thread Honza Král
On 2/20/07, kbochert <[EMAIL PROTECTED]> wrote: > > > > On Feb 19, 5:27 pm, "Lawrence Oluyede" <[EMAIL PROTECTED]> wrote: > > > All I can think of is to create a new model, say Poll1, with the > > > correct fields, do a syncdb, write and execute a python function to > > > transfer the data from Po

Re: Database changes

2007-02-19 Thread kbochert
On Feb 19, 5:27 pm, "Lawrence Oluyede" <[EMAIL PROTECTED]> wrote: > > All I can think of is to create a new model, say Poll1, with the > > correct fields, do a syncdb, write and execute a python function to > > transfer the data from Poll to Poll1, do a DROP TABLE on Poll, create > > a new tabl

Re: Database changes

2007-02-19 Thread Malcolm Tredinnick
On Tue, 2007-02-20 at 02:27 +0100, Lawrence Oluyede wrote: > > All I can think of is to create a new model, say Poll1, with the > > correct fields, do a syncdb, write and execute a python function to > > transfer the data from Poll to Poll1, do a DROP TABLE on Poll, create > > a new table named P

Re: Database changes

2007-02-19 Thread Adrian Holovaty
On 2/19/07, kbochert <[EMAIL PROTECTED]> wrote: > If I have a Django model: > > class Poll(models.Model): > ... > > and decide that I need another field in the table, how do I proceed > while keeping the data? Hi Karl, See the FAQ: "If I make changes to a model, how do I update the database

Re: Database changes

2007-02-19 Thread Lawrence Oluyede
> All I can think of is to create a new model, say Poll1, with the > correct fields, do a syncdb, write and execute a python function to > transfer the data from Poll to Poll1, do a DROP TABLE on Poll, create > a new table named Poll, do a syncdb transfer the data from Poll1 to > Poll with a pyth

Database changes

2007-02-19 Thread kbochert
If I have a Django model: class Poll(models.Model): ... and decide that I need another field in the table, how do I proceed while keeping the data? All I can think of is to create a new model, say Poll1, with the correct fields, do a syncdb, write and execute a python function to transfer t

Re: IPython Shell does not see database changes made by views.

2007-01-31 Thread Michael Radziej
Ivan Sagalaev: > Paul Childs wrote: >> I wanted to do some checks through the shell, which I was opened >> during my unit testing, and found that after making some queries using >> Django objects there appeared to be no changes in the database. When I >> checked the database using its admin tool t

Re: IPython Shell does not see database changes made by views.

2007-01-31 Thread Ivan Sagalaev
Paul Childs wrote: > I wanted to do some checks through the shell, which I was opened > during my unit testing, and found that after making some queries using > Django objects there appeared to be no changes in the database. When I > checked the database using its admin tool the changes were there

IPython Shell does not see database changes made by views.

2007-01-31 Thread Paul Childs
During unit testing I made changes to data in the database through my Django app. I wanted to do some checks through the shell, which I was opened during my unit testing, and found that after making some queries using Django objects there appeared to be no changes in the database. When I checked