On 17/05/07, Brian Cassidy <[EMAIL PROTECTED]> wrote:
Carl Franks wrote:
> I may be missing something, but I can't see any way of getting it
> starting with 'MyApp::Schema::Table'.
MyApp::Schema::Table->column_info( 'column' ) ?
Thanks! - I didn't know about that.
I've updated svn to now expec
Carl Franks wrote:
I've been getting the column info via:
MyApp::Schema->resultset('Table')->result_source->column_info;
I may be missing something, but I can't see any way of getting it
starting with 'MyApp::Schema::Table'.
MyApp::Schema::Table->result_source; gives a fatal error.
MyApp::Schem
On 17/05/07, Zbigniew Lukasiak <[EMAIL PROTECTED]> wrote:
Is there any reason to split the ResoultSet name to schema and table?
Why not use
constraints_from_dbic: [ 'MyApp::Schema::Table' ]
I've been getting the column info via:
MyApp::Schema->resultset('Table')->result_source->column_info;
My first thought was that those constraints should be generated into
the config files - just as I did in InstantCRUD, so that people can
modify them. But then actually it makes sense that the database
induced constraints are fixed. They are the minimal set of constraints
- so you only need to add
