On Thu, Dec 02, 2004 at 03:43:56AM -, Greg Sabino Mullane wrote:
> It also seems like an awful lot of overhead
> to make a module where a couple of lines in the script will
> suffice.
I don't really have an opinion on the module in question, but this logic
seems flawed to me.
I don't see how
On Fri, Nov 29, 2002 at 12:33:42PM +0100, Bart Lateur wrote:
> I hadn't looked at this thread until now, but now that I do, I do
> recognize the pattern. I've had the same kind of problems with Access.
> What can fix this, is having an explicit bind on the variable type,
> after the pepare phase, b
Class::DBI is a simple database->object mapping system. Simply point
it at your database, set up some classes to represent your tables,
tell it the relationships between your tables, and let it handle all
the 'simple' SQL for you (more complex queries can be written in SQL).
[See http:/
On Wed, Nov 27, 2002 at 02:51:08PM -0500, Ronald J Kimball wrote:
> > But what's the query being sent to MySQL? Why does it think that the
> > value is the column?
> I don't know how MySQL handles placeholders, so this is just a guess. It
> may simply be interpolating the string 'nine' into the qu
On Wed, Nov 27, 2002 at 08:28:40AM -0800, Michael A Chase wrote:
> On Wed, 27 Nov 2002 13:12:24 +0000 Tony Bowden <[EMAIL PROTECTED]> wrote:
> > And there's still the matter of the highly misleading error message:
> > DBD::mysql::st execute failed: Unknown column
On Mon, Nov 25, 2002 at 07:48:14AM -0800, Michael A Chase wrote:
> > I'm assuming that the first time the statement is executed something is
> > trying to work out whether the field is numeric or string, and seeing a
> > number, assumes it's numeric. But then, every future insert fails, with
> > a
Consider the following script:
#!/usr/bin/perl
use strict;
use warnings;
use DBI;
my $dbh = DBI->connect('dbi:mysql:music', 'user', 'pass');
my $insert = $dbh->prepare_cached(qq{
INSERT INTO user (username, password)
VALUES (?, ?)
});
my $delete = $dbh->prepar
On Wed, Jul 31, 2002 at 07:35:41PM +0100, Tim Bunce wrote:
> > Has anyone done a study which compares and contrasts the various
> > Object-Relational mapping systems that Tim mentions below?
> The only one I know of is
> http://poop.sourceforge.net
> I don't know how upto date it is.
Dave
On Tue, Jun 25, 2002 at 08:46:47AM +, william ross wrote:
> i notice that defining a relationship with might_have doesn't add a
> column to $class->__hasa_columns. is that something you're likely to
> change? it's enormously useful for me to be able to define relationship
> columns which mi
Class::DBI is a simple database->object mapping system. Simply point
it at your database, set up some classes to represent your tables,
tell it the relationships between your tables, and let it handle all
the 'simple' SQL for you (more complex queries can be written in SQL).
[See http:
sn't good enough, then there's always MySQL ;)
Tony
--
------
Tony Bowden | [EMAIL PROTECTED] | http://www.tmtm.com/
make me laugh make me cry enrage me don't try to disengage me
--
11 matches
Mail list logo
