On 7/2/07, Benjamin Slavin <[EMAIL PROTECTED]> wrote: > > > Hello. > > You mention you are using the multi-db branch. Do you get this > behavior in trunk?
i haven't tried this yet because i require multi-db functionality, so it does me no good if it works in trunk :) but i understand the value of trying this for debugging, and i will if it comes down to it. What happens if you update a user from within the Django management > shell? Does this result in a correct QuerySet from all()? yes. Are you under transaction management in the management shell? If so, > depending on the isolation level, this behavior may be expected. tell me more about transaction management -- i don't believe i'm using any, because there's nothing in my settings.py that would seem to apply, but perhaps i've overlooked something trivial. I think we're going to need a bit more information before we can be of > assistance (unless someone's seen this before). > > Also, Ben Ford has recently decided to wrestle with multi-db, and is > attempting to get his changes checked in... you may want to tune in to > the django-dev list to keep abreast of any updates on his progress and > code availability. thanks for the heads-up. i'm looking forward to multi-db getting more up-to-date. - Ben > > On 7/2/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > In case my original post was too unfriendly, here's my issue in plain > > terms: > > > > 1. I call model.objects.all() in an interactive shell > > 2. I modify the db directly in a different shell > > 3. I call model.objects.all() in the first shell again, and it doesn't > > pick up my changes. > > > > what's going on? i'm sure that the changes are actually committed in > > the db. should i post this in django-developers instead? > > > > On Jun 29, 1:29 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > > $ ./oui3/manage.py shell > > > Python 2.4.3 (#1, Jun 13 2006, 16:41:45) > > > [GCC 4.0.2 20051125 (Red Hat 4.0.2-8)] on linux2 > > > Type "help", "copyright", "credits" or "license" for more information. > > > (InteractiveConsole)>>> from oui3.mon.models import User > > > >>> User.objects.all() > > > > > > [<User: [EMAIL PROTECTED]>, <User: root>, <User: test-wsx>] > > > > > > (then, in another shell:) > > > > > > mysql> update user set username='test-wsy' where username='test-wsx'; > > > Query OK, 1 row affected (0.00 sec) > > > Rows matched: 1 Changed: 1 Warnings: 0 > > > > > > (back in the first shell:) > > > > > > >>> User.objects.all() > > > > > > [<User: [EMAIL PROTECTED]>, <User: root>, <User: test-wsx>] > > > > > > and yes, mysql auto-commit is on. > > > i'm using the multi-db branch. > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
