That's a very interesting thought Todd.
I don't know enough about Ruby to follow the code properly, but the
idea is pretty neat...
Re: Upgrading models... [without blowing away existing data]
Maybe mix your languages?
http://wiki.rubyonrails.com/rails/pages/UnderstandingMigrations
On 1/19/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> jobs:~/Projects/media mitch$ python manage.py sqlreset tunica | mysql
> --user=tunica --password=notmypassword tunica
> ERROR 1064 (42000) at line 18: You have an error in your SQL syntax;
> check the manual that corresponds to your MySQL
Along these same lines, I am trying to write some scripts to allow me
to automatically do a sqlreset and then reload data. The problem I'm
running into is that mysql dies when I pipe the output of the sqlreset
command to it. Specifically:
jobs:~/Projects/media mitch$ python manage.py sqlreset
Is there a preferred way to feed sample data to models? It would help in
this business of recreating databases over and over.
El lun, 26-12-2005 a las 21:07 -0600, James Bennett escribió:
> On 12/26/05, limodou <[EMAIL PROTECTED]> wrote:
> > I suggest that there may be a admin command just like:
On 12/26/05, limodou <[EMAIL PROTECTED]> wrote:
> May be sqlite can do like that, but other databases can not just
> remove the database file. And this appoach will destroy all the
> tables, but what I want may be just a single app, not the whole
> project. So if there is not a "reinstall"(or
2005/12/27, James Bennett <[EMAIL PROTECTED]>:
>
> On 12/26/05, limodou <[EMAIL PROTECTED]> wrote:
> > I suggest that there may be a admin command just like: django-admin.py
> > reinstall app
> > to do the things like: django-admin.py sqlreset appname | psql dbname
> >
> > I think this will be
On 12/26/05, limodou <[EMAIL PROTECTED]> wrote:
> I suggest that there may be a admin command just like: django-admin.py
> reinstall app
> to do the things like: django-admin.py sqlreset appname | psql dbname
>
> I think this will be helpful in developing period.
I'd be against it, just because
2005/12/27, quentinsf <[EMAIL PROTECTED]>:
>
> There's also some stuff here:
>
> http://code.djangoproject.com/wiki/DocumentationSuggestions
>
I suggest that there may be a admin command just like: django-admin.py
reinstall app
to do the things like: django-admin.py sqlreset appname | psql
There's also some stuff here:
http://code.djangoproject.com/wiki/DocumentationSuggestions
Quentin
On Tuesday 20 December 2005 09:37, Adrian Holovaty wrote:
> On 12/20/05, John Szakmeister <[EMAIL PROTECTED]> wrote:
> > Now onto the real reason I'm writing this email. There is great
> > flexibility in ORM layer, but the one thing that I haven't seen addressed
> > in any of the documentation
On 12/20/05, John Szakmeister <[EMAIL PROTECTED]> wrote:
> Now onto the real reason I'm writing this email. There is great flexibility
> in ORM layer, but the one thing that I haven't seen addressed in any of the
> documentation is upgrading the models. I don't always get them right the
> first
I am not sure about what you are asking, but this may help:
http://www.djangoproject.com/documentation/faq/#if-i-make-changes-to-a-model-how-do-i-update-the-database
First, let me say that I'm very impressed by Django and I want to both the
community and World Online for opening up such an impressive tool. I'm not a
web guy, but even I have been able to make use of it and create a few apps to
myself and other engineers do our jobs better.
Now onto the
14 matches
Mail list logo
