I was thinking it could work something like this:

directory model:

file public.py:
-classes defined here that are in "public" schema

file otherschema.py:
-classes defined here that are in "otherschema" schema


Something like that on top of being able to set a schemaname in sqlmeta would be nice (or maybe just use schemaname = __name__ to implement the above)? Of course, in mysql using the schema notation is the equivalent from using a different database, so what would be done about that?

On 12/30/05, Oleg Broytmann <phd@mail2.phd.pp.ru> wrote:
On Fri, Dec 30, 2005 at 12:01:12AM -0600, Igor Murashkin wrote:
> When using PostgreSQL, I noticed you can do
>
> class sqlmeta:
>    table = 'schemaname.tablename'
>
> However, this almost defeats the purpose of the tablename being
> automatically generated from the class name. Is there a way to specify a
> schema name, or maybe a prefix? How about some kind of namespace to use the
> schema?

   There is no currently.

> Just seems important, it's in ANSI after all.

   Patches will be gladly accepted.

Oleg.
--
     Oleg Broytmann            http://phd.pp.ru/            phd@phd.pp.ru
           Programmers don't die, they just GOSUB without RETURN.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
sqlobject-discuss mailing list
sqlobject-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss