<br><font size=2 face="sans-serif">Brian Cassidy wrote:</font>
<br><font size=2 face="sans-serif"> </font>
<br><font size=2 face="sans-serif">> Jon Warbrick wrote:</font>
<br><font size=2 face="sans-serif">> > Can a Catalyst::Model::DBIC::Schema
model be configured from a YAML </font>
<br><font size=2 face="sans-serif">> > file via Catalyst::Plugin::Config::YAML?
If so, how? Apologies if it's in </font>
<br><font size=2 face="sans-serif">> > the documentation somewhere,
but if so I've yet to find it...</font>
<br><font size=2 face="sans-serif">> > </font>
<br><font size=2 face="sans-serif">> in myapp.yml</font>
<br><font size=2 face="sans-serif">> </font>
<br><font size=2 face="sans-serif">> Model::MyModel:</font>
<br><font size=2 face="sans-serif">> schema_class: MySchema</font>
<br><font size=2 face="sans-serif">> connect_info:</font>
<br><font size=2 face="sans-serif">> - dbi:blahblah</font>
<br><font size=2 face="sans-serif">> - username</font>
<br><font size=2 face="sans-serif">> - password</font>
<br>
<br><font size=2 face="sans-serif">While we're on the subject, lets assume
that MySchema is 'myapp::SchemaLoader::foo.</font>
<br>
<br><font size=2 face="sans-serif">How do I make sure that my SchemaLoader
can see the config when it tries to execute</font>
<br><font size=2 face="sans-serif">__PACKAGE__->connection?</font>
<br>
<br><font size=2 face="sans-serif">It isn't seeing the Model::MyModel connect_info,
admonishing me for failing to provide </font>
<br><font size=2 face="sans-serif">connection info.</font>
<br>
<br><font size=2 face="sans-serif">Thanks.</font>
<br><font size=2 face="sans-serif">Len.</font>
<br>
<br>
<HTML><BODY><P><hr size=1></P><br>
<P><br>
This transmission may contain information that is privileged,<br>
confidential, legally privileged, and/or exempt from disclosure<br>
under applicable law. If you are not the intended recipient, you<br>
are hereby notified that any disclosure, copying, distribution, or<br>
use of the information contained herein (including any reliance<br>
thereon) is STRICTLY PROHIBITED. Although this transmission and<br>
any attachments are believed to be free of any virus or other<br>
defect that might affect any computer system into which it is<br>
received and opened, it is the responsibility of the recipient to<br>
ensure that it is virus free and no responsibility is accepted by<br>
JPMorgan Chase & Co., its subsidiaries and affiliates, as<br>
applicable, for any loss or damage arising in any way from its use.<br>
If you received this transmission in error, please immediately<br>
contact the sender and destroy the material in its entirety,<br>
whether in electronic or hard copy format. Thank you.<br>
</P></BODY></HTML>