On Jan 10, 2008 10:01 AM, Curon Davies <[EMAIL PROTECTED]> wrote:
> Hi John. Thanks for your help on this. Unfortunately that still
> doesn't quite work. If we do:
>
> $product = My::DB::Product->new(name => $^T);
> $product->add_prices(
> { price => 3.60, region => 'uk' },
> { price
Hi John. Thanks for your help on this. Unfortunately that still
doesn't quite work. If we do:
$product = My::DB::Product->new(name => $^T);
$product->add_prices(
{ price => 3.60, region => 'uk' },
{ price => 7.00, region => 'us' },
);
and then:
my @prices = $product->prices;
On Jan 10, 2008 5:47 AM, Curon Davies <[EMAIL PROTECTED]> wrote:
> Thanks for that suggestion, something that I didn't think about. The
> add_ prefix doesn't look that nice in the constructor.
Then don't put it in the constructor call :)
$product = My::DB::Product->new(name => $^T);
$product->add
On Jan 9, 2008 20:02, John Siracusa <[EMAIL PROTECTED]> wrote:
> In the meantime, you can always express more explicitly the operations
> you intend to perform. For example:
>
> $product = My::DB::Product->new(
> name => $^T,
> add_prices =>
> [
> { price => 3.60, region => 'uk' },
>
On Jan 9, 2008 2:05 PM, Curon Davies <[EMAIL PROTECTED]> wrote:
> The file works fine if the User (in this case 'rose_test') has DELETE
> permission the on 'price' table, but fails otherwise. From my
> prospective this should definitely not be the case, as the only action
> performed here is insert
The attaches file contains some code that I've put together which
reflects a situation that I have come across in our system, which has
different database permissions for different users, with users not
being granted more permissions than needed for their task.
The file works fine if the User (in
