Definitelly, we've been talking about this for a while now. Not sure if Tim
had something already set up for the next release???, but if not a patch
would be great!
Ilya
From: Matthew Wickline [mailto:[EMAIL PROTECTED]]
Would folks be interested in the option of specifying a
coderef for
I'm wondering what other people have developed as database
independent way(s) of determining if the insert or update being
done results in a duplicate key situation.
I can think of 2 methods to handle this:
1. before doing the insert or update, for *EACH AND EVERY*
unique key defined for
On Fri, 28 Sep 2001, gros wrote:
You could include an order by desc into your select
and limit the Output only to 1 row LIMIT 1.
If you're looking for a value extremity, you can always use the Max() or Min()
functions as well, which will return just one row.
--Arthur Corliss
On 2001-09-28, Hardy Merrill [EMAIL PROTECTED] wrote:
I can think of 2 methods to handle this:
1. before doing the insert or update, for *EACH AND EVERY* unique
key defined for a table, do a select with the where clause
looking for equality on all the fields in the unique key -
To install Oracle 8.1.7 on RH 7.1, you must first install the RH 6.2
compatibility packages (compat-egcs, compat-glibc and compat-libs) from the
7.1 CDs. Enter the following before running the Oracle installer:
export LD_ASSUME_KERNEL=2.2.5
. /usr/i386-glibc21-linux/bin/i386-glibc21-linux-env.sh
I am trying to export a table using dbd::db2 and failing miserably. I am
using DB2 v0.75; DBI v1.19 and perl v5.6.1 built for MSWin32-x86. And, we
are using DB2 5.2.
Here is a code snippet and the resulting error message. Any advice/sample
code etc would be greatly appreciated.
Thanks.
Mike
Is there a possibility to get only the last entry of a table ?
Sure, I could read the whole content into a loop but this is
IMHO not the best solution.
my $numFields = $sth-{'NUM_OF_FIELDS'};
while (my $ref = $sth-fetchrow_arrayref) {
for (my $i = 0; $i $numFields; $i++) {
You could include an order by desc into your select
and limit the Output only to 1 row LIMIT 1.
Hope that help?s
Guido
-Ursprungliche Nachricht-
Von: Mark Walter [mailto:[EMAIL PROTECTED]]
Gesendet: Freitag, 28. September 2001 12:40
An: [EMAIL PROTECTED]
Betreff: get
On Fri, 28 Sep 2001 12:46:52 +0200, gros wrote:
You could include an order by desc into your select
and limit the Output only to 1 row LIMIT 1.
Or just retrieve one record and -finish() if you don't have LIMIT.
--
Bart.
On Fri, 28 Sep 2001 17:06:17 -0400, Hardy Merrill wrote:
I'm wondering what other people have developed as database
independent way(s) of determining if the insert or update being
done results in a duplicate key situation.
I can think of 2 methods to handle this:
2. allow the database to
Hi Jeff,
I have a program listed below that shows what I think
is a bug.
you can call the script with these parameters:
-G user_name -D database -r
uncomment the line that is a select user_name() and
you will get this error:
The following actions have been performed:
DBD::ODBC::db do failed:
If I'm following through this correctly, this is not a bug. ODBC only allows
one active statement per connection. You are using the $hDB database handle
for this statement:
my $sth = $hDB-prepare( SQL );
select o.name
from sysobjects o, sysusers u
where
Mark Walter wrote:
Is there a possibility to get only the last entry of a table ?
You have to define last - rows are returned by a SQL query in no
particular order, unless you add an ORDER BY clause.
In a table with numbers,
SELECT * FROM my_table ORDER BY a_number desc LIMIT 1
will give
13 matches
Mail list logo
