dbix-datamodel Google Group

Re: [dbix-datamodel] result as array

s.zu...@gmail.com (Sergiy Zuban) — Tue, 14 May 2013 19:36:33 UT

Laurent,

In my case I don't have column handlers, but need to process big amount of
data as fast as possible (and keep using ORM to query db). Probably I'll go
ahead with -result_as => 'sth' and fetch data vi DBI.
Thank you for so fast reply.

--
Sergiy Zuban

Re: [dbix-datamodel] result as array

laurent.d...@free.fr (Laurent Dami) — Tue, 14 May 2013 19:19:34 UT

Le 14.05.2013 19:57, Sergiy Zuban a �crit :
Hi Sergiy,

The benefit of using an ORM is to give you objects on which you can
invoke methods. If all you want is raw data, then maybe you are better
off by calling DBI directly. Furthermore, all type conversions in DBIDM
depend on handlers associated to column names; so if that information is

result as array

s.zu...@gmail.com (Sergiy Zuban) — Tue, 14 May 2013 17:57:23 UT

Hi Laurent,
I'm trying to find a way to fetch data as arrays rather than hashes (as
statement/fast_statement does). In other words I need something similar to
DBI's $sth->fetchrow_arrayref.
From what I see in the code 'fast_statement' just binds columns to hash
values and technically it's possible to make this conditional and bind them

Re: [dbix-datamodel] Syntax change for bind options

s.zu...@gmail.com (Sergiy Zuban) — Fri, 19 Apr 2013 18:37:40 UT

Laurent,

Thank you informing about the change. Just tested new version - everything
works fine.

--
Sergiy Zuban

Syntax change for bind options

laurent.d...@justice.ge.ch (Dami Laurent (PJ)) — Thu, 18 Apr 2013 13:22:48 UT

Hi all,

Recently I added some support for specifying bind types (on request from Sergiy Zuban).
The initial syntax was as follows :

-where => { column => [ $orig_value, \%bind_type] }

This has the advantage of being very close to the DBI syntax

$sth->bind_param($num, $orig_value, \%bind_type)

Re: [dbix-datamodel] to_DB handler in WHERE

laurent.d...@free.fr (laurent dami) — Wed, 10 Apr 2013 21:04:28 UT

Le 10.04.2013 22:33, Sergiy Zuban a ï¿½crit :
Hi Sergiy,

Of course it would be ideal to automatically apply "to_DB handlers"
(a.k.a. deflators) within WHERE clauses; but unfortunately the way these
clauses are expressed within SQLA doesn't give us enough information to
automatically decide which handler goes where : there could be many

to_DB handler in WHERE

s.zu...@gmail.com (Sergiy Zuban) — Wed, 10 Apr 2013 20:33:49 UT

Hi Laurent,
Idea of to_DB/from_DB handlers is awesome, but it lacks support for WHERE
clause to make everything transparent.
I've been trying to automate this using dirty hack (using custom Statement
class with overridden *select* method) like this:
bless $where, $schema->table('Foo')->metadm- >class;

Re: [dbix-datamodel] DBIDM Failing Install 2.34

ross.attr...@gmail.com (Ross Attrill) — Wed, 10 Apr 2013 10:31:49 UT

Installs fine now.

Thank you Laurent.

Re: [dbix-datamodel] DBIDM Failing Install 2.34

laurent.d...@free.fr (laurent dami) — Tue, 09 Apr 2013 19:06:08 UT

Hum ... thanks, I forgot to publish SQLAM 1.12 on CPAN.
Done now.

Le 09.04.2013 12:44, Ross Attrill a �crit :

DBIDM Failing Install 2.34

ross.attr...@gmail.com (Ross Attrill) — Tue, 09 Apr 2013 10:44:25 UT

Hi Laurent,
Maybe this is transitory (looks like you are middle of releasing) but I
just noticed that DBIDM 2.34 is not installing from CPAN. Error messages
such as shown below.
Maybe your new version of DBIDM has filtered to CPAN before
SQL::Abstract::More so this is just timing.
Regards,
Ross.

Re: [dbix-datamodel] bind options

laurent.d...@free.fr (laurent dami) — Mon, 08 Apr 2013 20:11:01 UT

Le 08.03.2013 19:42, Sergiy Zuban a ï¿½crit :

Hi Sergiy,

I just uploaded v2.34 to CPAN, which implements support for specific types.
When you need to specify a type, replace the value by an arrayref of shape
[$original_value, \%datatype_spec]; this works for select(), insert()
and update().

Re: [dbix-datamodel] Cascaded Insert on Assocation - Not Just Composition?

ross.attr...@gmail.com (Ross Attrill) — Mon, 08 Apr 2013 02:51:10 UT

Hi Laurent - thank you very much for providing this fix.

I have done some initial testing and it works perfectly (of course).

I did have to go through my database schema and review my usage of cascaded
deletes as I got a few of these messages:

<Entity> can't be a component of <AnotherEntity> (already component of

Re: [dbix-datamodel] bind options

laurent.d...@free.fr (laurent dami) — Mon, 08 Apr 2013 01:12:53 UT

Le 08.03.2013 19:42, Sergiy Zuban a ï¿½crit :

Hi Sergiy,

I started studying this issue. While working on it, I came to a bug in
DBIx:DataModel : $statement->bind($num, $val, $type_attr) used the wrong
index when calling $sth->bind_param(...); it used a 0-based index while
DBI expects a 1-based index.

Re: [dbix-datamodel] Cascaded Insert on Assocation - Not Just Composition?

laurent.d...@free.fr (laurent dami) — Fri, 05 Apr 2013 08:03:48 UT

Le 05.04.2013 04:37, laurent dami a ï¿½crit :

Done; see last commit at [link]

Re: [dbix-datamodel] Cascaded Insert on Assocation - Not Just Composition?

ross.attr...@gmail.com (Ross Attrill) — Fri, 05 Apr 2013 03:38:52 UT

Hi Laurent,

I am using MS SQL Server with DBD::ODBC. For this RDBMS and DBD driver,
$dbh->foreign_key_info() definitely does seem to pull in the required
information:

'DELETE_RULE' => '1'

indicates 'No Action' while 0 indicates 'Cascade'.

Please let me know if I can help at all.