Thanks Bart,
I tried both your suggestions and they seem to work. I think I'm a bit
further on in understanding how this all fits together now.
Maria
On Thu, 25 Oct 2001, Bart Lateur wrote:
>
> Here. You're using fetch_row, which is intended to return a list/array,
> as a boolean i.e. in s
I've got a dbi application which is currently running happily on Oracle.
However, we have to port it to MySQL for some customers who don't have
Oracle and can't afford Oracle licenses.
I'm trying to do this is 2 stages. The first stage is to replace any
Oracle-specific SQL with generic SQL,
I've got an application developed using DBI, Oracle, and CGI. It works well
on this platform, but now I'm faced with the prospect or getting it to run
with a MySQL back end instead of Oracle. The differences between the two
implementations of SQL (especially date functions) are causing some prob
What you are trying to do looks suspiciously concurrent. How about a simpler
solution:
## snip##
$qh = $dbh->prepare("blabla");
$qh->execute;
print "SQL is busy processing your query, please wait ...\n";
@results = $qh->fetchrow_array;
print "... Processing complete.\n";
On Fri, 27 Apr 2001, Sterin, Ilya wrote:
> I believe in access you must enter date as "#02/03/1999#"
>
> Also your query is totally wrong, it's not
> "INSERT $date INTO table1
> VALUES($date)"
>
> but rather
>
> "insert into table 1 date values ($date)
Shouldn't that be:
insert into tab
Jim,
> my $in_clause1="('abcdef','xzyrst')";
> my $in_clause2="('abcdef')";
>
> sth=$db->prepare("select * from table_x where txt in ?");
> $sth->execute($in_clause1);
> # that works
> $sth->execute($in_clause);
> # this doesn't
I'm guessing you might have just included a typo in your example,
