<br><br><div><span class="gmail_quote">On 9/28/06, <b class="gmail_sendername"><a href="mailto:leonard.a.jaffe@jpmchase.com">leonard.a.jaffe@jpmchase.com</a></b> <<a href="mailto:leonard.a.jaffe@jpmchase.com">leonard.a.jaffe@jpmchase.com
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><font face="sans-serif" size="2">Brian Cassidy wrote:</font>
<br><font face="sans-serif" size="2"> </font>
<br><font face="sans-serif" size="2">> Jon Warbrick wrote:</font>
<br><font face="sans-serif" size="2">> > Can a Catalyst::Model::DBIC::Schema
model be configured from a YAML </font>
<br><font face="sans-serif" size="2">> > file via Catalyst::Plugin::Config::YAML?
If so, how? Apologies if it's in </font>
<br><font face="sans-serif" size="2">> > the documentation somewhere,
but if so I've yet to find it...</font>
<br><font face="sans-serif" size="2">> > </font>
<br><font face="sans-serif" size="2">> in myapp.yml</font>
<br><font face="sans-serif" size="2">> </font>
<br><font face="sans-serif" size="2">> Model::MyModel:</font>
<br><font face="sans-serif" size="2">> schema_class: MySchema</font>
<br><font face="sans-serif" size="2">> connect_info:</font>
<br><font face="sans-serif" size="2">> - dbi:blahblah</font>
<br><font face="sans-serif" size="2">> - username</font>
<br><font face="sans-serif" size="2">> - password</font>
<br>
<br><font face="sans-serif" size="2">While we're on the subject, lets assume
that MySchema is 'myapp::SchemaLoader::foo.</font>
<br>
<br><font face="sans-serif" size="2">How do I make sure that my SchemaLoader
can see the config when it tries to execute</font>
<br><font face="sans-serif" size="2">__PACKAGE__->connection?</font>
<br>
<br><font face="sans-serif" size="2">It isn't seeing the Model::MyModel connect_info,
admonishing me for failing to provide </font>
<br><font face="sans-serif" size="2">connection info.</font></blockquote><div><br><br>As with all things Perl, TIMTOWTDI. While you *can* specify the connection in the Schema, its generally not a great idea.<br><br>Best practice would be that myapp::SchemaLoader::foo should just contain the "loader_options" method, and really nothing else (no connect/connection call). Then when the Model makes the connection using your connect_info configuration, that's when the actual dynamic loading will happen.
<br><br>Even better practice would be to use the helper in create=static mode instead of create=dynamic, so that you're not re-scanning the table definitions at every server start. If you insist on maintaining your database the old-fashioned way (or have no control over it), you can regenerate via create=static each time there's a change in the DDL, and diff versus the previous version to see the changes, etc.
<br><br>The next step beyond that is to start maintaining your database tables using the generated DBIC schema and the SQLT/->deploy support. Then you won't need Loader at all.<br><br>Another good practice is to move the Schema definitions outside of the myapp:: Catalyst-app namespace, so that you can deploy the Schema independantly for other tools that might need access to your database.
<br></div><br>[maybe I should make a best practices section in the Schema::Loader pod?]<br><br>-- Brandon<br><br></div>