Andrew,
On Tue, Nov 9, 2010 at 2:15 AM, Andrew Kurinnyi <pri...@gmail.com> wrote:
> Hi Ramiro
>
> I've been working with Oracle during the sprints after last DjangoCon,
> and had the same problem. I've been told by several people that
> the second db can't be oracle and should be something else, like sqlite.
Thank you very much for your reply. I will test this tonight at home.
Karen had already given me some hints via IRC about havin
to use such a mutiple, heterogeneous DB scheme.
Thanks again for taking the time to share your experiences.
>
> Here is my db settings.
>
> DATABASES = {
> 'default': {
> 'ENGINE': 'django.db.backends.oracle', # Add 'postgresql_psycopg2',
> 'postgresql', 'mysql', 'sqlite3' or 'oracle'.
> 'NAME': 'XE', # Or path to database file if using
> sqlite3.
> 'USER': 'andrew', # Not used with sqlite3.
> 'PASSWORD': 'djangocon', # Not used with sqlite3.
> 'HOST': '192.168.2.33', # Set to empty string for
> localhost. Not used with sqlite3.
> 'PORT': '1521', # Set to empty string for
> default. Not used with sqlite3.
> },
> 'other': {
> 'ENGINE': 'django.db.backends.sqlite3', # Add 'postgresql_psycopg2',
> 'postgresql', 'mysql', 'sqlite3' or 'oracle'.
> 'NAME': 'other_db', # Or path to database file if
> using sqlite3.
> 'USER': '', # Not used with sqlite3.
> 'PASSWORD': '', # Not used with sqlite3.
> 'HOST': '', # Set to empty string for localhost.
> Not used with sqlite3.
> 'PORT': '', # Set to empty string for default.
> Not used with sqlite3.
> 'TEST_NAME': 'other_db',
> }
> }
>
> Andrew
>
--
Ramiro Morales
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
