no i want to use mysql and postgres parallel. On Thu, Mar 11, 2010 at 10:04 PM, Harsha Reddy <nhar...@gmail.com> wrote:
> And the database that you are using is? > By chance is it SQLite? > > I recently encountered such a requirement.. I am using django checked > out from the svn repo. > I solved it by doing something like this... > > def result(request): > DATABASES['default']['NAME']='./data/db/scenario1.db' > ... blah blah.. > > see if this approach help probably... > > Cheers!! > Harsha Reddy > > On Mar 11, 10:18 am, lakshmi silaja <lakshmi.sil...@gmail.com> wrote: > > thanks for ur suggestion jirka > > > > On Thu, Mar 11, 2010 at 3:01 AM, Jirka Vejrazka < > jirka.vejra...@gmail.com>wrote: > > > > > Hi Silaja, > > > > > first, I'm going to guess that no one will be able to solve your > > > problem. There are multiple reasons for it: > > > > > - Multiple database support is in Django 1.2. You insist on using it > > > on Django 1.1, without mentioning why you can't upgrade (the upgrade > > > would make sense for any reader not knowing the context that only you > > > currently do know) > > > - the code written by Eric F. is an interesting hack for older > > > versions of Django, but not too many people have probably used it, so > > > there would be little experience with that. However, there is a > > > problem: > > > - * you have not specified what your problem was when you tried it * > > > So, even people willing to spend their time helping you could not do > > > it as they would not know how far you have gotten implementing it and > > > what actually stopped you from succeeding. > > > - you mentioned "i.e some of rows in some "x" table in one database > > > and some of rows in "x" table in other database. i want to select > > > which database used to add/retrieve the rows dynamically". This is > > > quite complex and even the code from Eric's site will not help you > > > much. If you make it working, it will lay the foundations, but you'd > > > still be quite far from reaching your goal. > > > > > I'm afraid that you need to give us more detail and the actual > > > context before you can expect better answer than "upgrade to Django > > > 1.2". > > > > > Cheers > > > > > Jirka > > > > > -- > > > You received this message because you are subscribed to the Google > Groups > > > "Django users" group. > > > To post to this group, send email to django-us...@googlegroups.com. > > > To unsubscribe from this group, send email to > > > django-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@googlegroups.com> > <django-users%2bunsubscr...@googlegroups.com<django-users%252bunsubscr...@googlegroups.com> > > > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/django-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-us...@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
