I have just reconsidered these schema issues with Postgres and now think making the schema name mandatory is not a good idea.
First, you can't easily reuse an app written for MySQL or SQLite because you will need to add "public." to every table (data source) name. Second, you sometimes want to have unqualified table names. This way you can, for instance, use tables/views living in the schema named after the current user instead of the public tables/views. Therefore I just added a patch (http://trac.dabodev.com/ticket/1189) that makes schema names optional. It also improves some other issues with the Postgres code such as recognizing composite primary keys. -- Christoph _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
