From: jagdish eashwar
> the model. Disregarding the instruction not to modify anything above the
md5sum line, I changed the relationship name in People.pm from
> 'affiliation_id' to 'affiliation'. I could then access the affiliation_id
column in the People table without having to mention the relationship name.
> Nice. But what is the recommended way for getting around the problem of the
catalyst helper using the column name for the relationship
> name ? To what extent can one safely disregard the 'don't modify'
instruction?
You can disregard it entirely and make any change above that line, but you
won't be able to re-create the class files using the helper anymore, because if
the helper would re-create the modified (above that line) classes, it would
delete all the changes that you made above that line, and your app might not
work well because of this.
It could be helpful though if the helper would accept a parameter that tell
it to change all the classes that were not modified above that line, and create
separate classes with a .new extension for those classes that were changed. It
would be more flexible then, because we can still use it after we change some
classes above the checksum.
Until then... I've seen that the recommendation was to use the helper only
until you need to make changes above that line, and after that point, use the
classes as a base, and deploy them for changing the database.
(I don't know if this solution would work with any database type though...)
Anyway, does anyone have an example about how to do that deployment as easy
as possible?
Octavian
_______________________________________________
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/
