Re: And now with ContextualFetch

[prev] [thread] [next] [Date index for 2005/02/22]

From: Perrin Harkins
Subject: Re: And now with ContextualFetch
Date: 18:15 on 22 Feb 2005

On Tue, 2005-02-22 at 17:55 +0100, JJ Merelo wrote:
> Which, in English, is as much as saying that the column is of type
> integer but the expression is of type character varying, which it's
> _not_

Could be a problem with DBI identifying the type of data you're passing,
or it could be that the data you're passing is now what you think it is.

> Has anybody run into trouble when upgrading that module and running it
> under Class::DBI?

You pretty much have to run the latest version of ContextualFetch if you
want to run the latest Class::DBI.

- Perrin

(message missing)

Hairy problem with has_a and has_many
JJ Merelo 16:00 on 22 Feb 2005

Re: Hairy problem with has_a and has_many
Cees Hek 16:22 on 22 Feb 2005

Re: Hairy problem with has_a and has_many
Joss Shaw 16:24 on 22 Feb 2005

Re: Hairy problem with has_a and has_many
JJ Merelo 16:50 on 22 Feb 2005

And now with ContextualFetch
JJ Merelo 16:55 on 22 Feb 2005

Re: And now with ContextualFetch
Perrin Harkins 18:15 on 22 Feb 2005

Re: And now with ContextualFetch
JJ Merelo 18:25 on 22 Feb 2005

Re: Hairy problem with has_a and has_many
Perrin Harkins 18:17 on 22 Feb 2005

Re: And now with ContextualFetch
Perrin Harkins 18:41 on 22 Feb 2005

Re: And now with ContextualFetch
JJ Merelo 18:56 on 22 Feb 2005

RE: Hairy problem with has_a and has_many
Zhuang Li 20:03 on 23 Feb 2005

RE: Hairy problem with has_a and has_many
Zhuang Li 20:12 on 23 Feb 2005