encukou/test-1 — Issue #65: Specify the target schema
Author: encukou
Created: 2011-11-03 19:50:02+00:00
State: open
Labels: api, feature, involved, low-priority

**Reported by [Eevee](http://bugs.veekun.com/users/1) on 2011/04/28 05:16:25 +0000 · Migrated from [Redmine issue 598](http://bugs.veekun.com/issues/598)**

---

PostgreSQL (and any *real* database heh heh) support multiple schemata per database, which can be used for namespacing without the overhead of multiple databases (or the loss of joining between them).

SQLAlchemy, though, just reads and loads into/from the default. Would be nice if that weren’t the case.

I sense this will be a gigantic headache, as the schema doesn’t appear anywhere within the database URL syntax, and I think you’ll need to specify the schema when running *any* code that uses \`pokedex\`.

This is the best I could find on it: [http://stackoverflow.com/questions/2685899/schema-qualified-tables-with-sqlalchemy-sqlite-and-postgresql](http://stackoverflow.com/questions/2685899/schema-qualified-tables-with-sqlalchemy-sqlite-and-postgresql)

Redmine metadata:
Updated on: 2011/04/28 05:16:25 +0000
Start date: 2011/04/28