I would like to do this, but the policy at my workplace is to create our schema files with the script provided by Catalyst.
running the script from the command line looks something like this: perl script/myapp_create.pl model TestDatabase DBIC::Schema \ MyApp::Schema::TestDatabase ... So even if I went into the files and removed the unique constraint, my changes would get clobbered the next time someone edited our schema. Ash Berlin-2 wrote: > > > > > simple. Ignore the fact that Pg created a unique index to go with the > primary key - you created just a primary key, what Pg does is > irrelevant. > > i.e. get rid of the add_unique_constraint. That is only needed if you > explicitly create (and want to search on) a subsequent unique > constraint. > > -ash > > _______________________________________________ > List: Catalyst@lists.scsys.co.uk > Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst > Searchable archive: > http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ > Dev site: http://dev.catalyst.perl.org/ > > -- View this message in context: http://www.nabble.com/create-model-tp21503833p21756961.html Sent from the Catalyst Web Framework mailing list archive at Nabble.com. _______________________________________________ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
