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
> 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
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
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
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
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
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
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
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.
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
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
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
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
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
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
15 matches
Mail list logo
