Getting to the bottom of the ordering of loading and inheritance in
general in Maypole is pretty infuriating at times.
I don't know the answer to your problem but does changing your code
to this help?
Package MyDB;
#config and relationship stuff
{
Package MyDB::MyTable;
sub display_columns {
#etc
}
# untaint rules and other stuff
# the second one won't work with Class::DBI::Loader.
}
On 21 Dec 2005, at 10:41, Kim Ryan wrote:
Here is an example
This works fine
I declare a list of tables to display with config->display_tables
sub MyDB::MyTable::display_columns
{
qw(
job_type
version
col_a
col_b)
}
This does not produce a warning, but reverts to displaying all
columns in
alphabetical order, ignoring the display_column method
sub MyDB::my_table::display_columns
{
qw(
job_type
version
col_a
col_b)
}
This one on the other hand will be quietly ignored, because you're
implicitly creating a new class my_table. Does it die if you use
strict?
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Maypole-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/maypole-users
