On 26 Nov 2006, at 15:31, Nilson Santos Figueiredo Junior wrote:
Hopefully that test case will be enough. However, I've encountered
situations where it worked alright for some data sets. It's somewhat
dependant on the data *and* on the order_by clause of your query
(sometimes the same query
Anthony Hinsinger wrote:
Hi Anthony,
I've the same problem, and I think the only solution to resolve it is
to modify the code. DBIC (i think) assumes that join conditions are
all based on the '=' operator. For DBMS, join condition is an
expression resulting in a value of type boolean.
I'm
Since I have a current DBIC working copy on my HD now, I also offer this
patch to be applied. It lets you set an inflator for multiple columns
at once, as described in my email one month ago:
http://lists.scsys.co.uk/pipermail/dbix-class/2006-October/002687.html
--
Bernhard Graf
---
Bernhard Graf wrote:
Anthony Hinsinger wrote:
Hi Anthony,
I've the same problem, and I think the only solution to resolve it is
to modify the code. DBIC (i think) assumes that join conditions are
all based on the '=' operator. For DBMS, join condition is an
expression resulting in a value of
Except it won't for much longer, as we're making the values to/from
inflate/deflate insist on being blessed() objects.
Though I'm pretty sure one of them did already, so do freeze/thaw return
objects, or something?
Jess
On Sun, 26 Nov 2006, Mike Friedman wrote:
On 11/26/06, Ash Berlin
On 11/27/06, Jess Robinson [EMAIL PROTECTED] wrote:
Except it won't for much longer, as we're making the values to/from
inflate/deflate insist on being blessed() objects.
Why? That seems a bit draconian.
Though I'm pretty sure one of them did already, so do freeze/thaw return
objects, or
On 11/24/06, Sam Crawley [EMAIL PROTECTED] wrote:
Sounds good... but I'm unclear on how inflate_column gets the schema
of the 'foreign' database. Does this need to be passed to the original
schema at some point, so it's row
objects can access it?
You could make your inflate_column methods
