Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
  Reporter:  Simon Willison| Owner:  Alex   
  
Status:  closed| Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:  fixed |  Keywords:  multiple 
database feature
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Changes (by jb0t):

 * cc: erik.engbre...@gmail.com, gary.wil...@gmail.com,
 farcep...@gmail.com, ei...@eikke.com, peter.k...@ijs.si,
 chris.mca...@gmail.com, ferri...@gmail.com, iac...@m0n5t3r.info,
 andrewjwilkin...@gmail.com, em...@chrisbraybrook.com,
 daryl.spit...@gmail.com, re...@diji.biz, mzdan...@gmail.com,
 rik...@gmail.com, stua...@kcbbs.gen.nz, jholloway7+dja...@gmail.com,
 simeonf+dja...@gmail.com, knyght+dja...@gmail.com, sp...@spoofa.info,
 dja...@flypig.net, fl...@n-schlachter.de, tarkatro...@gmail.com,
 alexandru.pal...@loopback.ro, jb0t, lao, alexkoshelev, _wilane,
 daemondazz, S2nek, swa...@gmail.com, andrew.krasn...@gmail.com,
 da...@brightscope.com, isometry (removed)

Comment:

 I know posts should be focused on ticket problems or solutions, but I
 can't help myself.

 thank you so much!  what a great Christmas gift!

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

--

You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
  Reporter:  Simon Willison| Owner:  Alex   
  
Status:  closed| Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:  fixed |  Keywords:  multiple 
database feature
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Changes (by Alex):

  * status:  new => closed
  * resolution:  => fixed

Comment:

 Fixed in r11952 :D

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

--

You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
  Reporter:  Simon Willison| Owner:  Alex   
  
Status:  new   | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:|  Keywords:  multiple 
database feature
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Changes (by isometry):

 * cc: isometry (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

--

You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
  Reporter:  Simon Willison| Owner:  Alex   
  
Status:  new   | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:|  Keywords:  multiple 
database feature
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Changes (by anonymous):

 * cc: da...@brightscope.com (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
  Reporter:  Simon Willison| Owner:  Alex   
  
Status:  new   | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:|  Keywords:  multiple 
database feature
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Changes (by bioform):

 * cc: andrew.krasn...@gmail.com (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
  Reporter:  Simon Willison| Owner:  Alex   
  
Status:  new   | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:|  Keywords:  multiple 
database feature
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Changes (by xdrum):

 * cc: swa...@gmail.com (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
  Reporter:  Simon Willison| Owner:  Alex   
  
Status:  new   | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:|  Keywords:  multiple 
database feature
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Comment (by Alex):

 If you want to see the current state of work please use my branch in
 soc2009/multidb in the Django repository, right now my GitHub repo is
 undergoing severe code alterations that make it high unstable.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
  Reporter:  Simon Willison| Owner:  Alex   
  
Status:  new   | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:|  Keywords:  multiple 
database feature
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Comment (by russellm):

 Replying to [comment:72 nicktank]:
 > Replying to [comment:66 alexkoshelev]:
 >  I've implemented this on a development version of django 1.1.
 ...
 > I apologize if this isn't the place to report this issue.  I am new
 around here and to django in general.

 Nick - as noted in comment 64, Multiple database connections was the
 subject of a 2009 Google Summer of Code project. Alex Gaynor has been
 developing the code to implement this. It's not a minor change - it
 requires lots of changes throughout Django.
 [http://github.com/alex/django/tree/multiple-db Check out Alex's GitHub
 repository] if you want to see the progress he has made. It isn't quite
 ready for trunk yet, but it's getting close, and it's sufficiently
 functional that you can try it out.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
  Reporter:  Simon Willison| Owner:  Alex   
  
Status:  new   | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:|  Keywords:  multiple 
database feature
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Comment (by nicktank):

 Replying to [comment:66 alexkoshelev]:
  I've implemented this on a development version of django 1.1.  It appears
 as though it appends the table name of the app in the database established
 in the project settings instead of adding the model's tables to the
 declared database
 {{{

 from django.db import models
 from django.blocks.apps.core.managers import MultiDBManager

 class FireMap(models.Model):
 address = models.CharField(max_length=100)
 city = models.CharField(max_length=50)
 zip = models.IntegerField()
 latitude = models.DecimalField(max_digits=17, decimal_places=14)
 longitude = models.DecimalField(max_digits=17, decimal_places=14)
 neighborhood = models.CharField(max_length=30)
 assesorID = models.IntegerField()
 assessorURL = models.URLField()
 homeValue = models.CommaSeparatedIntegerField(max_length=8)
 homeOwner = models.CharField (max_length=30)
 mainIMGURL = models.URLField()
 photos = models.CommaSeparatedIntegerField(max_length=40)
 articleID1 = models.IntegerField()
 articleID2 = models.IntegerField()
 articleID3 = models.IntegerField()
 extrainfo = models.TextField()

 objects = MultiDBManager()

 def __str__(self):
 return self.name

 class Meta:
 db_name = 'firemap'
 }}}

 the setting for the Db in my project settings file is set to:

 {{{

 DATABASE_ENGINE = 'postgresql_psycopg2'   # 'postgresql_psycopg2',
 'postgresql', 'mysql', 'sqlite3' or 'oracle'.
 DATABASE_NAME = 'newsok' # Or path to database file if using
 sqlite3.

 }}}

 When the tables are created I see in the newsok Db a firemap_firemap table
 (firemap is the name of the app as well) but there is nothing in the
 actual firemap Db.

 I apologize if this isn't the place to report this issue.  I am new around
 here and to django in general.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
  Reporter:  Simon Willison| Owner:  Alex   
  
Status:  new   | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:|  Keywords:  multiple 
database feature
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Changes (by anonymous):

 * cc: S2nek (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
  Reporter:  Simon Willison| Owner:  Alex   
  
Status:  new   | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:|  Keywords:  multiple 
database feature
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Changes (by eengbrec):

 * cc: eengbrec (removed)
 * cc: erik.engbre...@gmail.com (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
  Reporter:  Simon Willison| Owner:  Alex   
  
Status:  new   | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:|  Keywords:  multiple 
database feature
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Changes (by eengbrec):

 * cc: eengbrec (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
  Reporter:  Simon Willison| Owner:  Alex   
  
Status:  new   | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:|  Keywords:  multiple 
database feature
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Changes (by anonymous):

 * cc: daemondazz (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
  Reporter:  Simon Willison| Owner:  Alex   
  
Status:  new   | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:|  Keywords:  multiple 
database feature
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Changes (by _wilane):

 * cc: _wilane (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
  Reporter:  Simon Willison| Owner:  Alex   
  
Status:  new   | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:|  Keywords:  multiple 
database feature
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Changes (by alexkoshelev):

 * cc: alexkoshelev (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
  Reporter:  Simon Willison| Owner:  Alex   
  
Status:  new   | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:|  Keywords:  multiple 
database feature
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Comment (by kimus):

 I made a Multiple database manager for django-blocks see: http://django-
 blocks.googlecode.com/svn/trunk/src/python/blocks/apps/core/managers.py

 just need to do something like this to your model:
 {{{
 #!python
 from django.db import models from blocks.apps.core.managers import
 MultiDBManager

 class SomeModel(models.Model):
 code = models.IntegerField(primary_key=True)
 name = models.CharField(max_length=250)

 objects = MultiDBManager()

 class Meta:
 db_name = 'oracle'
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
  Reporter:  Simon Willison| Owner:  Alex   
  
Status:  new   | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:|  Keywords:  multiple 
database feature
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Changes (by Alex):

  * owner:  darylspitzer => Alex
  * status:  assigned => new
  * stage:  Someday/Maybe => Accepted

Comment:

 This ticket is accepted as a part of the 2009 GSOC.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
  Reporter:  Simon Willison| Owner:  
darylspitzer 
Status:  assigned  | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:|  Keywords:  multiple 
database feature
 Stage:  Someday/Maybe | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Comment (by lao):

 (idea #10492)
  My look is
 {{{
 #!python
 # Wrapper classes
 from re import compile

 class Db:
 def __init__(self, cstr):
 self.link = None
 __re_dbstr =
 
compile(r'^(?P[^:]+)://((?P[^\(:]+)(\((?P.+)\))?(:(?P[...@]+))?(@(?P[^\/:]+)(:(?P\d+))?)?)?/(?P.+)')
 try:
 self.__db = __re_dbstr.search(cstr).groupdict()
 # Fix for sqlite
 if self.__db['engine'].startswith('sqlite'):
 self.__db['name'] = "/%s" % self.__db['name']
 except:
 self.__db = {}
 raise Exception("#1")
 self.connect()

 def connect(self):
 self.link = 'Connection link'   # 

 def keys(self):
return self.__db.keys()

 def items(self):
return self.__db.items()

 def __getitem__(self, key):
 return self.__db.get(key, None)

 def __getattr__(self, key):
 return self.__db.get(key, None)


 class DbPool:
def __init__(self):
self.__dbs = {}
self.__default = None

def __getitem__(self, db_alias):
if db_alias not in self.__dbs:
raise Exception('#2')
return self.__dbs[db_alias]

def __getattr__(self, key):
if not self.__default:
   raise Exception('#3')
return self.__dbs[ self.__default ].__getattr__(key)

def add(self, db_alias, db_str):
self.__dbs[db_alias] = Db(db_str)
if self.__default:
return
self.set_default(db_alias)

def get_default(self):
return self.__default

def set_default(self, dbAlias):
if dbAlias in self.__dbs:
self.__default = dbAlias
else:
raise Exception("#4")

 # Settings
 DATABASES = {
 'alpha': 'sqlite3:///:memory:',
 'beta': 'sqlite3:///tmp/django.sqlite3',
 'gamma': 'mysql://user1/django',
 'delta': 'mysql://user1:password1/django',
 'default': 'mysql://user1:passwo...@host1/django',
 'reserv1': 'mysql://user1:passwo...@host1:1234/django',
 'reserv2': 'postgresql://user1(role1):passwo...@host1/django',
 'etc': 'postgresql://user1(role1):passwo...@host1:1234/django',
 }
 DATABASE_DEFAULT = 'default'
 DATABASE_OPTIONS = {}
 DATABASE_OPTIONS['etc'] = {
'ssl':'...'
 }
 # Setting handlers
 pool = DbPool()

 for dbase in DATABASES.items():
 pool.add(*dbase)

 pool.set_default(DATABASE_DEFAULT)
 # Default database
 print pool.engine, pool.host, pool.name

 # Some other db
 print pool['etc'].engine, pool['etc'].host, pool['etc'].name

 # Models
 class SomeModel():
 # If not defined
 # meta_connections = [DATABASE_DEFAULT]
 meta_connections = ['alpha', 'beta']

 # API
 # instead
 # from django.db import connection
 # connection.cursor()
 #
 # use
 # from django.db import pool
 # pool.link.cursor()
 # pool['etc'].link.cursor()
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
  Reporter:  Simon Willison| Owner:  
darylspitzer 
Status:  assigned  | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:|  Keywords:  multiple 
database feature
 Stage:  Someday/Maybe | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Changes (by lao):

 * cc: lao (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
  Reporter:  Simon Willison| Owner:  
darylspitzer 
Status:  assigned  | Milestone:  post-1.0   
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:|  Keywords:  multiple 
database feature
 Stage:  Someday/Maybe | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Changes (by anonymous):

 * cc: jb0t (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
  Reporter:  Simon Willison| Owner:  
darylspitzer 
Status:  assigned  | Milestone:  post-1.0   
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:|  Keywords:  multiple 
database feature
 Stage:  Someday/Maybe | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Changes (by anonymous):

 * cc: [EMAIL PROTECTED] (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@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-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
  Reporter:  Simon Willison| Owner:  
darylspitzer 
Status:  assigned  | Milestone:  post-1.0   
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:|  Keywords:  multiple 
database feature
 Stage:  Someday/Maybe | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Comment (by mtredinnick):

 There has, in fact, been lots of activity. Perhaps you might wish to
 peruse the archives of django-developers, which is where design work takes
 place. This ticket is really just a placeholder that will be closed when
 we commit some kind of final solution (and possibly for patches as we get
 closer if the work is self-contained enough not to require a branch).

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@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-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
  Reporter:  Simon Willison| Owner:  
darylspitzer 
Status:  assigned  | Milestone:  post-1.0   
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:|  Keywords:  multiple 
database feature
 Stage:  Someday/Maybe | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Changes (by Tarken):

 * cc: [EMAIL PROTECTED] (added)

Comment:

 What is the current status on this issue? There doesn't appear to have
 been any visible movement in several months now, and this is something
 which would be very useful in a project I'm working on. I have a slightly
 different use case than the previously mentioned ones, however... and I'm
 sure it's not an entirely common one, but perhaps something to take into
 consideration.

 The company I work for is sitting on a fairly large data warehouse for a
 number of clients. Each client has their own database, with a common
 schema, on one of two MS SQL 2k servers. In the near future, we will
 hopefully be moving some of these clients onto a PostgreSQL server (and in
 the distant future, it would be nice to move towards Greenplum; although
 that should be transparent with psycopg2, afaik). In addition, there is a
 separate database already running on the PostgreSQL server, which stores
 configuration parameters and which I am using for the Django system
 tables.

 On every page load, I need Django to connect to database 'A' on the
 PostgreSQL server for any Django specific operations, then connect to an
 arbitrary database on either of the MS SQL servers, depending on which of
 our clients' data is currently being viewed. From what I've seen so far in
 the discussion in this ticket and on MultipleDatabaseSupport, this doesn't
 sound like it would likely be a supported scenario, as the connection to
 be used is determined dynamically, rather than a static connection chosen
 per model. In my case, all models apply across all database connections.

 Now, I have made this work thus far with my own connection manager
 (http://dpaste.com/hold/84458/) but using it is somewhat kludgy and I'm
 sure it's far from a full implementation. I also had to apply a hack
 (http://code.google.com/p/django-pyodbc/issues/detail?id=18) to django-
 pyodbc and apply a pending patch (#6710) to Django in order to get it to
 work. Here is an example of why it in use: http://dpaste.com/hold/84465/

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@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-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
 Reporter:  Simon Willison |Owner:  adrian
 Type:  task   |   Status:  new   
 Priority:  normal |Milestone:
Component:  django-admin.py|  Version:  SVN   
 Severity:  normal |   Resolution:
 Keywords:  rthml tab space editor js  |  
---+
Changes (by anonymous):

 * cc: [EMAIL PROTECTED] (added)

-- 
Ticket URL: 
Django 
The web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@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-updates
-~--~~~~--~~--~--~---

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
 Reporter:  Simon Willison |Owner:  adrian
 Type:  task   |   Status:  new   
 Priority:  normal |Milestone:
Component:  django-admin.py|  Version:  SVN   
 Severity:  normal |   Resolution:
 Keywords:  rthml tab space editor js  |  
---+
Changes (by adrian):

  * priority:  highest => normal
  * severity:  trivial => normal

-- 
Ticket URL: 
Django 
The web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@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-updates
-~--~~~~--~~--~--~---

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
 Reporter:  Simon Willison |Owner:  adrian
 Type:  task   |   Status:  new   
 Priority:  highest|Milestone:
Component:  django-admin.py|  Version:  SVN   
 Severity:  trivial|   Resolution:
 Keywords:  rthml tab space editor js  |  
---+
Comment (by anonymous):

 What is current status of this?  When can we expect to see this in trunk?
 
 thanks,
 Forest

-- 
Ticket URL: 
Django 
The web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@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-updates
-~--~~~~--~~--~--~---

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
--+-
 Reporter:  Simon Willison|Owner:  adrian
 Type:  enhancement   |   Status:  new   
 Priority:  low   |Milestone:
Component:  Database wrapper  |  Version:
 Severity:  normal|   Resolution:
 Keywords:|  
--+-
Comment (by anonymous):

 I would have to agree that this is a serious limitation.
 It is not always possible to restructure existing databases into a single
 database for use and it would be of great valu to be able to use the
 django database model to integrate multiple databases at some level.

-- 
Ticket URL: 
Django 
The web framework for perfectionists with deadlines.

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
--+-
 Reporter:  Simon Willison|Owner:  adrian
 Type:  enhancement   |   Status:  new   
 Priority:  low   |Milestone:
Component:  Database wrapper  |  Version:
 Severity:  normal|   Resolution:
 Keywords:|  
--+-
Changes (by adrian):

  * priority:  normal => low
  * severity:  major => normal

-- 
Ticket URL: 
Django 
The web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@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-updates
-~--~~~~--~~--~--~---