Don't consider this a bug report yet - since I'm still in the process
of narrowing this down and getting a small test case failing.
However, just in case it rings any "of course its Foo" bells I /
appear/ to be seeing
Rose::DB::Object::Loader::make_classes causing a segfault when
running und
On 2 Apr 2007, at 12:49, Adrian Howard wrote:
> Don't consider this a bug report yet - since I'm still in the process
> of narrowing this down and getting a small test case failing.
[snip]
Ignore me. Blame a dodgy DBD::mysql install.
Adrian
-
I have a request for the docs:
I'm adding a new table with 2 unique indexes / keys on it , one of
which is a multiple column key. the docs are really unclear on how
thats done in the setup.
example:
unique keys are:
1- single col - 'hex_id'
2- mult co
On 4/2/07, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
> doc change:
> with_managers seems to default to true , it should be listed as such
It is. File: lib/Rose/DB/Object/Loader.pm
...
=item B
If true, create
L-derived manager
classes for each L subclass. Defaults to the value
of the l
On 4/2/07, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
> I'm adding a new table with 2 unique indexes / keys on it , one of
> which is a multiple column key. the docs are really unclear on how
> thats done in the setup.
http://search.cpan.org/dist/Rose-DB-Object/lib/Rose/DB/Object/Metadata.pm#uni
On Apr 2, 2007, at 11:45 AM, John Siracusa wrote:
> It is. File: lib/Rose/DB/Object/Loader.pm
oh, thats tricky. i read those docs like crazy trying to figure out
what was going on.
> ...but did what instead?
everything as-is , except for the omission of that line. I like
having the she
Hi all,
Never used Rose::DB before, but I've heard enough good things about it
that I'm giving it a try. Some of what I'm writing is probably clunky,
so pointers welcome.
I'm trying to provide my own metadata class and I've run into a problem
I don't quite understand. Here's my base class:
p
Irrelevant side note:
> __PACKAGE__->meta->setup(
> table => 'os',
> columns => [
> os => {
> type=> 'varchar',
> length => 31,
> primary_key => 1,
> not_null=> 1
> },
> type
On 4/2/07, [EMAIL PROTECTED] wrote:
> sub setup {
> my ( $self, %arg_for ) = @_;
> $self->SUPER::setup(%arg_for);
> foreach my $column ( $self->columns ) {
> my $name = $column->name;
>
> # here's the problem
> $self->alias_column( $name => "_$name"
--- John Siracusa <[EMAIL PROTECTED]> wrote:
> sub add_columns
> {
> my($self) = shift;
>
> my @added_columns = $self->SUPER::add_columns(@_);
>
> foreach my $column (@added_columns )
> {
> $self->alias_column($column->name => '_' . $column->name)
>
On 4/2/07, Ovid <[EMAIL PROTECTED]> wrote:
> I didn't see it in the docs, but is there anything akin to 'mutator'
> metadata which would let me do something like the following?
>
> foreach my $method ( $class->mutators ) {
> $self->make_override( $method );
> }
>
> The 'mutators' would retu
11 matches
Mail list logo
