Peter Rabbitson wrote:
David Ihnen wrote:
Ivan Fomichev wrote:
Hello, great module. Instead of arguing if it is a useful patch or not
and if it should be applied or there are weird workarounds easily
available, just make your own DBIx::Class component and release it on
CPAN. Who need
On Tue, Jun 30, 2009 at 11:14, David Ihnendav...@norchemlab.com wrote:
But the question seemed to be 'I don't understand why you would need this'
and 'is there a need for this feature' and I must vociferously respond IT
IS USEFULE and YES THERE IS. As for 'is there a need to do it this way'
David Ihnen wrote:
Peter Rabbitson wrote:
David Ihnen wrote:
Ivan Fomichev wrote:
Hello, great module. Instead of arguing if it is a useful patch or not
and if it should be applied or there are weird workarounds easily
available, just make your own DBIx::Class component and release
Rob Kinyon wrote:
Now, if someone can provide a solid use-case, then I'll be onboard.
But, adding features for the sake of adding features is how you end up
with a crappy API.
Rob
Lets see if I can argue the use case. I tripped over this limitation
and I *think* it was when I was doing this
Hello,
Is it possible to have a dry run mode in DBIx-Class ?
I just want to see the SQL Statements DBIx would execute, but not want
DBIx to execute them.
This way I can verify the statements before executing.
Is this possible ?
---
Robert Heinzmann
DBD::Mock was built specifically for this.
Rob
On Tue, Jun 30, 2009 at 12:35, Robert
Heinzmannrobert.heinzm...@1und1.de wrote:
Hello,
Is it possible to have a dry run mode in DBIx-Class ?
I just want to see the SQL Statements DBIx would execute, but not want
DBIx to execute them.
This
Am 30.06.2009 um 18:10 schrieb David Ihnen:
Rob Kinyon wrote:
Now, if someone can provide a solid use-case, then I'll be onboard.
But, adding features for the sake of adding features is how you end
up
with a crappy API.
Rob
Lets see if I can argue the use case. I tripped over this
