Using views doesn't seem to be a workable option. I tried using them, but then DBIC complained that they don't have primary keys. So I guess I have to reconcile myself to putting all the tables in one database.
jagdish On Thu, Jul 3, 2008 at 11:09 PM, Bruce J Keeler <[EMAIL PROTECTED]> wrote: > jagdish eashwar wrote: > >> Putting all the tables in one database is a solution. I am afraid, >> however, that when I create a model using script/MyApp_create.pl for a >> specific Catalyst application, I'll get all the tables in the database >> into my DBIC schema. Is there a way of making MyApp_create.pl pick up >> only a subset of the tables? >> >> jagdish >> >> O >> > > I don't know if mysql has a facility similar to Oracle's synonyms whereby > you could alias tables from the common schema into the app-specific one. If > not, it's possible that a simple views might work, something like: > > create view employee as (select * from common.employee) > > Then just put all of the tables into the same DBIC schema. > > > _______________________________________________ > List: [email protected] > Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst > Searchable archive: > http://www.mail-archive.com/[email protected]/ > Dev site: http://dev.catalyst.perl.org/ >
_______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
