RE: [sqlite] What does this mean???
From: "Anderson, James H (IT)" <[EMAIL PROTECTED]> Reply-To: sqlite-users@sqlite.org To: Subject: [sqlite] What does this mean??? Date: Wed, 7 Feb 2007 17:33:21 -0500 not an error(21) at dbdimp.c line 398 I'm using DBD::SQLite and got this error. What does it mean and how best to hanle it? Thanks, jim NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error. _ Latest updates from the world of sports http://content.msn.co.in/Sports/Default - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] What does this mean???
WOW. Good to know. Thanks Jim (and Matt). -Clark - Original Message From: "Anderson, James H (IT)" <[EMAIL PROTECTED]> To: Matt Sergeant <[EMAIL PROTECTED]> Cc: sqlite-users@sqlite.org Sent: Thursday, February 8, 2007 8:36:31 AM Subject: RE: [sqlite] What does this mean??? Looks like removing the semi-colon did the trick. Thanks very much. -Original Message- From: Matt Sergeant [mailto:[EMAIL PROTECTED] Sent: Thursday, February 08, 2007 11:09 AM To: Anderson, James H (IT) Cc: sqlite-users@sqlite.org Subject: Re: [sqlite] What does this mean??? On 8-Feb-07, at 11:04 AM, Anderson, James H ((IT)) wrote: > The output after setting $dbh->trace(3): Ah. Please re-try after taking the semi-colon off the end of your SQL. NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error. - To unsubscribe, send email to [EMAIL PROTECTED] - - To unsubscribe, send email to [EMAIL PROTECTED] -
RE: [sqlite] What does this mean???
Looks like removing the semi-colon did the trick. Thanks very much. -Original Message- From: Matt Sergeant [mailto:[EMAIL PROTECTED] Sent: Thursday, February 08, 2007 11:09 AM To: Anderson, James H (IT) Cc: sqlite-users@sqlite.org Subject: Re: [sqlite] What does this mean??? On 8-Feb-07, at 11:04 AM, Anderson, James H ((IT)) wrote: > The output after setting $dbh->trace(3): Ah. Please re-try after taking the semi-colon off the end of your SQL. NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error. - To unsubscribe, send email to [EMAIL PROTECTED] -
RE: [sqlite] What does this mean???
The output after setting $dbh->trace(3): insert or replace into TMP_credDerivOrig select A.date, A.CDId, A.CDName, A.CDTicket, A.tradeId, A.tapsAccount, A.CDBook, coalesce(A.CDFid,'') CDFid, A.CDStatus, A.CDTradeDate, A.CDExpDate, A.CDNotional, A.CDCurr, A.CDSellBuy, A.CDType, A.CDExerType, A.CDEntity, A.CDCusip, A.CDSetlType, A.CDCredInit, A.CDSingleEntry, A.CDMaterialType, A.CDEffDate, A.CDPremFreq, A.CDPaymentType, A.CDUpfrontSetl, A.CDPublicInfo, A.CDCollReq, A.CDSpreadCurve, A.CDPremium, A.CDOptType, A.CDAccrue, A.CDRefPrice, A.CDPremiumAmnt, A.CDLastCoupLength, A.CDWhoDelivers, A.CDCollateralText, A.CDFactorReason, A.CDDefStartProt, A.CDDefEndProt, A.CDDefProtType, B.CDComment, A.CDEvent, A.CDCurveType, A.CrvShName, A.CDRefEntity, A.CDRefIndustry, A.CDRefCountry, A.CDRefSNP, A.CDRefMoody, A.CDRefMSRating, A.CDRefId from TMP_credDerivOrig A, C1_credDerivComment B where A.CDId = B.CDId; -> prepare for DBD::SQLite::db (DBI::db=HASH(0x8159970)~0x8389c6c ' insert or replace into TMP_credDerivOrig select A.date, A.CDId, A.CDName, A.CDTicket, A.tradeId, A.tapsAccount, A.CDBook, coalesce(A.CDFid,'') CDFid, A.CDStatus, A.CDTradeDate, A.CDExpDate, A.CDNotional, A.CDCurr, A.CDSellBuy, A.CDType, A.CDExerType, A.CDEntity, A.CDCusip, A.CDSetlType, A.CDCredInit, A.CDSingleEntry, A.CDMaterialType, A.CDEffDate, A.CDPremFreq, A.CDPaymentType, A.CDUpfrontS...') thr#813b008 dbih_setup_handle(DBI::st=HASH(0x8390cb8)=>DBI::st=HASH(0x8389d8c), DBD::SQLite::st, 8390c88, Null!) dbih_make_com(DBI::db=HASH(0x8389c6c), 838a0b8, DBD::SQLite::st, 124, 0) thr#813b008 sqlite trace: prepare statement: insert or replace into TMP_credDerivOrig select A.date, A.CDId, A.CDName, A.CDTicket, A.tradeId, A.tapsAccount, A.CDBook, coalesce(A.CDFid,'') CDFid, A.CDStatus, A.CDTradeDate, A.CDExpDate, A.CDNotional, A.CDCurr, A.CDSellBuy, A.CDType, A.CDExerType, A.CDEntity, A.CDCusip, A.CDSetlType, A.CDCredInit, A.CDSingleEntry, A.CDMaterialType, A.CDEffDate, A.CDPremFreq, A.CDPaymentType, A.CDUpfrontSetl, A.CDPublicInfo, A.CDCollReq, A.CDSpreadCurve, A.CDPremium, A.CDOptType, A.CDAccrue, A.CDRefPrice, A.CDPremiumAmnt, A.CDLastCoupLength, A.CDWhoDelivers, A.CDCollateralText, A.CDFactorReason, A.CDDefStartProt, A.CDDefEndProt, A.CDDefProtType, B.CDComment, A.CDEvent, A.CDCurveType, A.CrvShName, A.CDRefEntity, A.CDRefIndustry, A.CDRefCountry, A.CDRefSNP, A.CDRefMoody, A.CDRefMSRating, A.CDRefId from TMP_credDerivOrig A, C1_credDerivComment B where A.CDId = B.CDId; at dbdimp.c line 258 <- prepare= DBI::st=HASH(0x8390cb8) at DBUtilLite.pm line 185 via at DBUtilLite.pm line 185 -> DESTROY for DBD::SQLite::st (DBI::st=HASH(0x8390b80)~INNER) thr#813b008 <- DESTROY= undef at DBUtilLite.pm line 186 via at DBUtilLite.pm line 186 -> execute for DBD::SQLite::st (DBI::st=HASH(0x8390cb8)~0x8389d8c) thr#813b008 sqlite trace: Execute returned 0 cols at dbdimp.c line 391 <- execute= 566606 at DBUtilLite.pm line 187 via at DBUtilLite.pm line 187 -> rows for DBD::SQLite::st (DBI::st=HASH(0x8390cb8)~0x8389d8c) thr#813b008 <- rows= 566606 at DBUtilLite.pm line 189 via at test.pl line 29 rows affected: 566606 -> prepare for DBD::SQLite::db (DBI::db=HASH(0x8159970)~0x8389c6c ' ') thr#813b008 dbih_setup_handle(DBI::st=HASH(0x8390cc4)=>DBI::st=HASH(0x8390a6c), DBD::SQLite::st, 8390ca0, Null!) dbih_make_com(DBI::db=HASH(0x8389c6c), 838a0b8, DBD::SQLite::st, 124, 0) thr#813b008 sqlite trace: prepare statement: at dbdimp.c line 258 <- prepare= DBI::st=HASH(0x8390cc4) at DBUtilLite.pm line 185 via at DBUtilLite.pm line 185 -> DESTROY for DBD::SQLite::st (DBI::st=HASH(0x8389d8c)~INNER) thr#813b008 <- DESTROY= undef at DBUtilLite.pm line 186 via at DBUtilLite.pm line 186 -> execute for DBD::SQLite::st (DBI::st=HASH(0x8390cc4)~0x8390a6c) thr#813b008 sqlite trace: Execute returned 0 cols at dbdimp.c line 391 sqlite error 21 recorded: not an error at dbdimp.c line 398 !! ERROR: 21 'not an error(21) at dbdimp.c line 398' (err#0) <- execute= undef at DBUtilLite.pm line 187 via at DBUtilLite.pm line 187 1 -> FETCH for DBD::SQLite::st (DBI::st=HASH(0x8390a6c)~INNER 'ParamValues') thr#813b008 .. FETCH DBI::st=HASH(0x8390a6c) 'ParamValues' = undef ERROR: 21 'not an error(21) at dbdimp.c line 398' (err#0) 1 <- FETCH= undef at DBUtilLite.pm line 187 via at DBUtilLite.pm line 187 DBD::SQLite::st execute failed: not an error(21) at dbdimp.c line 398 [for Statement " "] at /u/crdceed/lib/perl5/DBUtilLite.pm line 187. DBD::SQLite::st execute failed: not an error(21) at dbdimp.c line 398 [for Statement " "] at /u/crdceed/lib/perl5/DBUtilLite.pm line 187. -> DESTROY for DBD::SQLite::st (DBI::st=HASH(0x8390a6c)~INNER) thr#813b008 ERROR: 21 'not an error(21) at dbdimp.c line 398' (err#0) <- DESTROY= undef -> DESTROY for DBD::SQLite::db (DBI::db=HASH(0x8389c6c)~INNER) thr#813b008 ERROR: 21 'not an error(21) at dbdimp.c line 398' (err#0) <-
RE: [sqlite] What does this mean???
I get the exact same failure after making the suggested changes.
DBD::SQLite::st execute failed: not an error(21) at dbdimp.c line 398
[for Statement "
"] at /u/crdceed/lib/perl5/DBUtilLite.pm line 185.
DBD::SQLite::st execute failed: not an error(21) at dbdimp.c line 398
[for Statement "
"] at /u/crdceed/lib/perl5/DBUtilLite.pm line 185.
-Original Message-
From: Clark Christensen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 07, 2007 7:30 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] What does this mean???
Jim,
Line 398 in dbdimp.c appears to be in DBD-SQLite's $sth->execute code.
I agree with Puneet. If you wrap your DBI calls in eval blocks and test
$@, you might get more info about the error (or maybe not). Also,
setting RaiseError, and ShowErrorStatement in $dbh wouldn't hurt.
$dbh = DBI->connect("dbi:SQLite:dbname=$dbname","","",
{RaiseError=>1, ShowErrorStatement=>1});
$sql = "insert or replace into...";
eval { $sth = $dbh->prepare( $sql ) };
die $@ if ($@);
eval { $sth->execute };
die $@ if ($@);
Not sure if any of that helps at all. "not an error" on $sth->execute
is bound to be nasty to diagnose. FWIW, it looks like "not an error" is
the result of a call to sqlite3_errmsg().
Unrelated to your issue is a DBI presentation you may be interested to
look through at
http://search.cpan.org/src/TIMB/DBI_AdvancedTalk_2004/index.htm
-Clark
- Original Message
From: "Anderson, James H (IT)" <[EMAIL PROTECTED]>
To: sqlite-users@sqlite.org
Sent: Wednesday, February 7, 2007 3:28:00 PM
Subject: RE: [sqlite] What does this mean???
Yes, I printed out the errstr. That was what I sent in the original
mail.
$sth = $dbh->prepare( $sql ) or die $dbh->errstr;
$sth->executeor die $dbh->errstr;
which produced:
not an error(21) at dbdimp.c line 398
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of P
Kishor
Sent: Wednesday, February 07, 2007 6:16 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] What does this mean???
On 2/7/07, Anderson, James H (IT) <[EMAIL PROTECTED]>
wrote:
> Context :)
>
> insert or replace into TMP_credDerivOrig
> select
> A.date,
..
> A.CDRefId
> from TMP_credDerivOrig A,
>C1_credDerivComment B
> where A.CDId = B.CDId;
yes, but you want to know why an error is appearing, so you have to
show the code that is causing the error. The above is just the SQL
statement. How on earth can one decipher whether or not you have some
error in your code from that.
Did you print out the DBI err str? Did you wrap it in an eval and then
print out the reason it died? That would really help find the cause of
the error.
Else, you can always open up dbdimp.c and look at line 398. That
should set you in the right direction.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of P
> Kishor
> Sent: Wednesday, February 07, 2007 5:39 PM
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] What does this mean???
>
> On 2/7/07, Anderson, James H (IT) <[EMAIL PROTECTED]>
> wrote:
> > not an error(21) at dbdimp.c line 398
> >
> > I'm using DBD::SQLite and got this error. What does it mean and how
> best
> > to hanle it?
> >
>
>
> well, how about some context? What is the structure of the table(s)
> you are querying, what is the query, the relevant code snippet,
> something to go on?
>
> The error string itself means that you did something via Perl that
> violated whatever it was at line 398 of the c program dbdimp.c.
>
> --
> Puneet Kishor http://punkish.eidesis.org/
> Nelson Inst. for Env. Studies, UW-Madison http://www.nelson.wisc.edu/
> Open Source Geospatial Foundation http://www.osgeo.org/education/
> -
> collaborate, communicate, compete
> =
>
>
> -
> To unsubscribe, send email to [EMAIL PROTECTED]
>
> -
>
>
> NOTICE: If received in error, please destroy and notify sender. Sender
does not intend to waive confidentiality or privilege. Use of this email
is prohibited when received in error.
>
--
Puneet Kishor http://punkish.eidesis.org/
Nelson Inst. for Env. Studies, UW-Madison http://www.nelson.wisc.edu/
Open Source Geospatial Foundation http://www.
RE: [sqlite] What does this mean???
Found the following in sqlite.h.in. This indicates to me that DBD-SQLite
isn't handling this "error" string correctly.
/*
** Return the error code for the most recent sqlite3_* API call
associated
** with sqlite3 handle 'db'. SQLITE_OK is returned if the most recent
** API call was successful.
**
** Calls to many sqlite3_* functions set the error code and string
returned
** by sqlite3_errcode(), sqlite3_errmsg() and sqlite3_errmsg16()
** (overwriting the previous values). Note that calls to
sqlite3_errcode(),
** sqlite3_errmsg() and sqlite3_errmsg16() themselves do not affect the
** results of future invocations.
**
** Assuming no other intervening sqlite3_* API calls are made, the error
** code returned by this function is associated with the same error as
** the strings returned by sqlite3_errmsg() and sqlite3_errmsg16().
*/
int sqlite3_errcode(sqlite3 *db);
/*
** Return a pointer to a UTF-8 encoded string describing in english the
** error condition for the most recent sqlite3_* API call. The returned
** string is always terminated by an 0x00 byte.
**
** The string "not an error" is returned when the most recent API call
was
** successful.
*/
const char *sqlite3_errmsg(sqlite3*);
/*
** Return a pointer to a UTF-16 native byte order encoded string
describing
** in english the error condition for the most recent sqlite3_* API
call.
** The returned string is always terminated by a pair of 0x00 bytes.
**
** The string "not an error" is returned when the most recent API call
was
** successful.
*/
const void *sqlite3_errmsg16(sqlite3*);
-Original Message-
From: Clark Christensen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 07, 2007 7:30 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] What does this mean???
Jim,
Line 398 in dbdimp.c appears to be in DBD-SQLite's $sth->execute code.
I agree with Puneet. If you wrap your DBI calls in eval blocks and test
$@, you might get more info about the error (or maybe not). Also,
setting RaiseError, and ShowErrorStatement in $dbh wouldn't hurt.
$dbh = DBI->connect("dbi:SQLite:dbname=$dbname","","",
{RaiseError=>1, ShowErrorStatement=>1});
$sql = "insert or replace into...";
eval { $sth = $dbh->prepare( $sql ) };
die $@ if ($@);
eval { $sth->execute };
die $@ if ($@);
Not sure if any of that helps at all. "not an error" on $sth->execute
is bound to be nasty to diagnose. FWIW, it looks like "not an error" is
the result of a call to sqlite3_errmsg().
Unrelated to your issue is a DBI presentation you may be interested to
look through at
http://search.cpan.org/src/TIMB/DBI_AdvancedTalk_2004/index.htm
-Clark
- Original Message ----
From: "Anderson, James H (IT)" <[EMAIL PROTECTED]>
To: sqlite-users@sqlite.org
Sent: Wednesday, February 7, 2007 3:28:00 PM
Subject: RE: [sqlite] What does this mean???
Yes, I printed out the errstr. That was what I sent in the original
mail.
$sth = $dbh->prepare( $sql ) or die $dbh->errstr;
$sth->executeor die $dbh->errstr;
which produced:
not an error(21) at dbdimp.c line 398
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of P
Kishor
Sent: Wednesday, February 07, 2007 6:16 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] What does this mean???
On 2/7/07, Anderson, James H (IT) <[EMAIL PROTECTED]>
wrote:
> Context :)
>
> insert or replace into TMP_credDerivOrig
> select
> A.date,
..
> A.CDRefId
> from TMP_credDerivOrig A,
>C1_credDerivComment B
> where A.CDId = B.CDId;
yes, but you want to know why an error is appearing, so you have to
show the code that is causing the error. The above is just the SQL
statement. How on earth can one decipher whether or not you have some
error in your code from that.
Did you print out the DBI err str? Did you wrap it in an eval and then
print out the reason it died? That would really help find the cause of
the error.
Else, you can always open up dbdimp.c and look at line 398. That
should set you in the right direction.
> -----Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of P
> Kishor
> Sent: Wednesday, February 07, 2007 5:39 PM
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] What does this mean???
>
> On 2/7/07, Anderson, James H (IT) <[EMAIL PROTECTED]>
> wrote:
> > not an error(21) at dbdimp.c line 398
> >
> > I'm using DBD::SQLite and got this error. What does it mean and how
> best
> > to hanle it?
> >
>
>
> well, how about some context? What is the structure of the table(s)
> you are querying, what is the query, the relevant code snippet,
> something to go on?
>
> The error string itself means tha
RE: [sqlite] What does this mean???
Thanks, Clark. I'll give that a try.
jim
-Original Message-
From: Clark Christensen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 07, 2007 7:30 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] What does this mean???
Jim,
Line 398 in dbdimp.c appears to be in DBD-SQLite's $sth->execute code.
I agree with Puneet. If you wrap your DBI calls in eval blocks and test
$@, you might get more info about the error (or maybe not). Also,
setting RaiseError, and ShowErrorStatement in $dbh wouldn't hurt.
$dbh = DBI->connect("dbi:SQLite:dbname=$dbname","","",
{RaiseError=>1, ShowErrorStatement=>1});
$sql = "insert or replace into...";
eval { $sth = $dbh->prepare( $sql ) };
die $@ if ($@);
eval { $sth->execute };
die $@ if ($@);
Not sure if any of that helps at all. "not an error" on $sth->execute
is bound to be nasty to diagnose. FWIW, it looks like "not an error" is
the result of a call to sqlite3_errmsg().
Unrelated to your issue is a DBI presentation you may be interested to
look through at
http://search.cpan.org/src/TIMB/DBI_AdvancedTalk_2004/index.htm
-Clark
- Original Message
From: "Anderson, James H (IT)" <[EMAIL PROTECTED]>
To: sqlite-users@sqlite.org
Sent: Wednesday, February 7, 2007 3:28:00 PM
Subject: RE: [sqlite] What does this mean???
Yes, I printed out the errstr. That was what I sent in the original
mail.
$sth = $dbh->prepare( $sql ) or die $dbh->errstr;
$sth->executeor die $dbh->errstr;
which produced:
not an error(21) at dbdimp.c line 398
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of P
Kishor
Sent: Wednesday, February 07, 2007 6:16 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] What does this mean???
On 2/7/07, Anderson, James H (IT) <[EMAIL PROTECTED]>
wrote:
> Context :)
>
> insert or replace into TMP_credDerivOrig
> select
> A.date,
..
> A.CDRefId
> from TMP_credDerivOrig A,
>C1_credDerivComment B
> where A.CDId = B.CDId;
yes, but you want to know why an error is appearing, so you have to
show the code that is causing the error. The above is just the SQL
statement. How on earth can one decipher whether or not you have some
error in your code from that.
Did you print out the DBI err str? Did you wrap it in an eval and then
print out the reason it died? That would really help find the cause of
the error.
Else, you can always open up dbdimp.c and look at line 398. That
should set you in the right direction.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of P
> Kishor
> Sent: Wednesday, February 07, 2007 5:39 PM
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] What does this mean???
>
> On 2/7/07, Anderson, James H (IT) <[EMAIL PROTECTED]>
> wrote:
> > not an error(21) at dbdimp.c line 398
> >
> > I'm using DBD::SQLite and got this error. What does it mean and how
> best
> > to hanle it?
> >
>
>
> well, how about some context? What is the structure of the table(s)
> you are querying, what is the query, the relevant code snippet,
> something to go on?
>
> The error string itself means that you did something via Perl that
> violated whatever it was at line 398 of the c program dbdimp.c.
>
> --
> Puneet Kishor http://punkish.eidesis.org/
> Nelson Inst. for Env. Studies, UW-Madison http://www.nelson.wisc.edu/
> Open Source Geospatial Foundation http://www.osgeo.org/education/
> -
> collaborate, communicate, compete
> =
>
>
> -
> To unsubscribe, send email to [EMAIL PROTECTED]
>
> -
>
>
> NOTICE: If received in error, please destroy and notify sender. Sender
does not intend to waive confidentiality or privilege. Use of this email
is prohibited when received in error.
>
--
Puneet Kishor http://punkish.eidesis.org/
Nelson Inst. for Env. Studies, UW-Madison http://www.nelson.wisc.edu/
Open Source Geospatial Foundation http://www.osgeo.org/education/
-
collaborate, communicate, compete
=
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
Re: [sqlite] What does this mean???
Jim,
Line 398 in dbdimp.c appears to be in DBD-SQLite's $sth->execute code.
I agree with Puneet. If you wrap your DBI calls in eval blocks and test $@,
you might get more info about the error (or maybe not). Also, setting
RaiseError, and ShowErrorStatement in $dbh wouldn't hurt.
$dbh = DBI->connect("dbi:SQLite:dbname=$dbname","","", {RaiseError=>1,
ShowErrorStatement=>1});
$sql = "insert or replace into...";
eval { $sth = $dbh->prepare( $sql ) };
die $@ if ($@);
eval { $sth->execute };
die $@ if ($@);
Not sure if any of that helps at all. "not an error" on $sth->execute is bound
to be nasty to diagnose. FWIW, it looks like "not an error" is the result of a
call to sqlite3_errmsg().
Unrelated to your issue is a DBI presentation you may be interested to look
through at http://search.cpan.org/src/TIMB/DBI_AdvancedTalk_2004/index.htm
-Clark
- Original Message
From: "Anderson, James H (IT)" <[EMAIL PROTECTED]>
To: sqlite-users@sqlite.org
Sent: Wednesday, February 7, 2007 3:28:00 PM
Subject: RE: [sqlite] What does this mean???
Yes, I printed out the errstr. That was what I sent in the original
mail.
$sth = $dbh->prepare( $sql ) or die $dbh->errstr;
$sth->executeor die $dbh->errstr;
which produced:
not an error(21) at dbdimp.c line 398
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of P
Kishor
Sent: Wednesday, February 07, 2007 6:16 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] What does this mean???
On 2/7/07, Anderson, James H (IT) <[EMAIL PROTECTED]>
wrote:
> Context :)
>
> insert or replace into TMP_credDerivOrig
> select
> A.date,
..
> A.CDRefId
> from TMP_credDerivOrig A,
>C1_credDerivComment B
> where A.CDId = B.CDId;
yes, but you want to know why an error is appearing, so you have to
show the code that is causing the error. The above is just the SQL
statement. How on earth can one decipher whether or not you have some
error in your code from that.
Did you print out the DBI err str? Did you wrap it in an eval and then
print out the reason it died? That would really help find the cause of
the error.
Else, you can always open up dbdimp.c and look at line 398. That
should set you in the right direction.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of P
> Kishor
> Sent: Wednesday, February 07, 2007 5:39 PM
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] What does this mean???
>
> On 2/7/07, Anderson, James H (IT) <[EMAIL PROTECTED]>
> wrote:
> > not an error(21) at dbdimp.c line 398
> >
> > I'm using DBD::SQLite and got this error. What does it mean and how
> best
> > to hanle it?
> >
>
>
> well, how about some context? What is the structure of the table(s)
> you are querying, what is the query, the relevant code snippet,
> something to go on?
>
> The error string itself means that you did something via Perl that
> violated whatever it was at line 398 of the c program dbdimp.c.
>
> --
> Puneet Kishor http://punkish.eidesis.org/
> Nelson Inst. for Env. Studies, UW-Madison http://www.nelson.wisc.edu/
> Open Source Geospatial Foundation http://www.osgeo.org/education/
> -
> collaborate, communicate, compete
> =
>
>
> -
> To unsubscribe, send email to [EMAIL PROTECTED]
>
> -
>
>
> NOTICE: If received in error, please destroy and notify sender. Sender
does not intend to waive confidentiality or privilege. Use of this email
is prohibited when received in error.
>
--
Puneet Kishor http://punkish.eidesis.org/
Nelson Inst. for Env. Studies, UW-Madison http://www.nelson.wisc.edu/
Open Source Geospatial Foundation http://www.osgeo.org/education/
-
collaborate, communicate, compete
=
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
NOTICE: If received in error, please destroy and notify sender. Sender does not
intend to waive confidentiality or privilege. Use of this email is prohibited
when received in error.
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
RE: [sqlite] What does this mean???
Yes, I printed out the errstr. That was what I sent in the original mail. $sth = $dbh->prepare( $sql ) or die $dbh->errstr; $sth->executeor die $dbh->errstr; which produced: not an error(21) at dbdimp.c line 398 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of P Kishor Sent: Wednesday, February 07, 2007 6:16 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] What does this mean??? On 2/7/07, Anderson, James H (IT) <[EMAIL PROTECTED]> wrote: > Context :) > > insert or replace into TMP_credDerivOrig > select > A.date, .. > A.CDRefId > from TMP_credDerivOrig A, >C1_credDerivComment B > where A.CDId = B.CDId; yes, but you want to know why an error is appearing, so you have to show the code that is causing the error. The above is just the SQL statement. How on earth can one decipher whether or not you have some error in your code from that. Did you print out the DBI err str? Did you wrap it in an eval and then print out the reason it died? That would really help find the cause of the error. Else, you can always open up dbdimp.c and look at line 398. That should set you in the right direction. > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of P > Kishor > Sent: Wednesday, February 07, 2007 5:39 PM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] What does this mean??? > > On 2/7/07, Anderson, James H (IT) <[EMAIL PROTECTED]> > wrote: > > not an error(21) at dbdimp.c line 398 > > > > I'm using DBD::SQLite and got this error. What does it mean and how > best > > to hanle it? > > > > > well, how about some context? What is the structure of the table(s) > you are querying, what is the query, the relevant code snippet, > something to go on? > > The error string itself means that you did something via Perl that > violated whatever it was at line 398 of the c program dbdimp.c. > > -- > Puneet Kishor http://punkish.eidesis.org/ > Nelson Inst. for Env. Studies, UW-Madison http://www.nelson.wisc.edu/ > Open Source Geospatial Foundation http://www.osgeo.org/education/ > - > collaborate, communicate, compete > = > > > - > To unsubscribe, send email to [EMAIL PROTECTED] > > - > > > NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error. > -- Puneet Kishor http://punkish.eidesis.org/ Nelson Inst. for Env. Studies, UW-Madison http://www.nelson.wisc.edu/ Open Source Geospatial Foundation http://www.osgeo.org/education/ - collaborate, communicate, compete = - To unsubscribe, send email to [EMAIL PROTECTED] - NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error. - To unsubscribe, send email to [EMAIL PROTECTED] -
RE: [sqlite] What does this mean???
sqlite-version: 3.3.5
DBD-SQLite: 1.12
-Original Message-
From: Clark Christensen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 07, 2007 6:15 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] What does this mean???
What version of SQLite, and what version of DBD-SQLite?
I saw this predictably with DBD-SQLite 1.09 and SQLite 3.2.7 where I did
something like:
$sth = $dbh->prepare("select foo, bar from mytable where rowid =
?");
for $i (1..5) {
($myfoo, $mybar) = $dbh->selectrow_array($sth, undef, $i);
}
It would work for the first iteration, then raise a "not an error" error
on the second. It was annoying, but I usually just worked around it
using $sth->execute/bind_columns/fetch inside the loop.
I updated to DBD-SQLite 1.13 with SQLite 3.3.12, and it worked like it's
documented for DBI (fixed the problem).
-Clark
- Original Message
From: "Anderson, James H (IT)" <[EMAIL PROTECTED]>
To: sqlite-users@sqlite.org
Sent: Wednesday, February 7, 2007 2:33:21 PM
Subject: [sqlite] What does this mean???
not an error(21) at dbdimp.c line 398
I'm using DBD::SQLite and got this error. What does it mean and how best
to hanle it?
Thanks,
jim
NOTICE: If received in error, please destroy and notify sender. Sender
does not intend to waive confidentiality or privilege. Use of this email
is prohibited when received in error.
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
NOTICE: If received in error, please destroy and notify sender. Sender does not
intend to waive confidentiality or privilege. Use of this email is prohibited
when received in error.
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
Re: [sqlite] What does this mean???
On 2/7/07, Anderson, James H (IT) <[EMAIL PROTECTED]> wrote: Context :) insert or replace into TMP_credDerivOrig select A.date, .. A.CDRefId from TMP_credDerivOrig A, C1_credDerivComment B where A.CDId = B.CDId; yes, but you want to know why an error is appearing, so you have to show the code that is causing the error. The above is just the SQL statement. How on earth can one decipher whether or not you have some error in your code from that. Did you print out the DBI err str? Did you wrap it in an eval and then print out the reason it died? That would really help find the cause of the error. Else, you can always open up dbdimp.c and look at line 398. That should set you in the right direction. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of P Kishor Sent: Wednesday, February 07, 2007 5:39 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] What does this mean??? On 2/7/07, Anderson, James H (IT) <[EMAIL PROTECTED]> wrote: > not an error(21) at dbdimp.c line 398 > > I'm using DBD::SQLite and got this error. What does it mean and how best > to hanle it? > well, how about some context? What is the structure of the table(s) you are querying, what is the query, the relevant code snippet, something to go on? The error string itself means that you did something via Perl that violated whatever it was at line 398 of the c program dbdimp.c. -- Puneet Kishor http://punkish.eidesis.org/ Nelson Inst. for Env. Studies, UW-Madison http://www.nelson.wisc.edu/ Open Source Geospatial Foundation http://www.osgeo.org/education/ - collaborate, communicate, compete = - To unsubscribe, send email to [EMAIL PROTECTED] - NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error. -- Puneet Kishor http://punkish.eidesis.org/ Nelson Inst. for Env. Studies, UW-Madison http://www.nelson.wisc.edu/ Open Source Geospatial Foundation http://www.osgeo.org/education/ - collaborate, communicate, compete = - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] What does this mean???
What version of SQLite, and what version of DBD-SQLite?
I saw this predictably with DBD-SQLite 1.09 and SQLite 3.2.7 where I did
something like:
$sth = $dbh->prepare("select foo, bar from mytable where rowid = ?");
for $i (1..5) {
($myfoo, $mybar) = $dbh->selectrow_array($sth, undef, $i);
}
It would work for the first iteration, then raise a "not an error" error on the
second. It was annoying, but I usually just worked around it using
$sth->execute/bind_columns/fetch inside the loop.
I updated to DBD-SQLite 1.13 with SQLite 3.3.12, and it worked like it's
documented for DBI (fixed the problem).
-Clark
- Original Message
From: "Anderson, James H (IT)" <[EMAIL PROTECTED]>
To: sqlite-users@sqlite.org
Sent: Wednesday, February 7, 2007 2:33:21 PM
Subject: [sqlite] What does this mean???
not an error(21) at dbdimp.c line 398
I'm using DBD::SQLite and got this error. What does it mean and how best
to hanle it?
Thanks,
jim
NOTICE: If received in error, please destroy and notify sender. Sender does not
intend to waive confidentiality or privilege. Use of this email is prohibited
when received in error.
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
RE: [sqlite] What does this mean???
Context :) insert or replace into TMP_credDerivOrig select A.date, A.CDId, A.CDName, A.CDTicket, A.tradeId, A.tapsAccount, A.CDBook, coalesce(A.CDFid,'') CDFid, A.CDStatus, A.CDTradeDate, A.CDExpDate, A.CDNotional, A.CDCurr, A.CDSellBuy, A.CDType, A.CDExerType, A.CDEntity, A.CDCusip, A.CDSetlType, A.CDCredInit, A.CDSingleEntry, A.CDMaterialType, A.CDEffDate, A.CDPremFreq, A.CDPaymentType, A.CDUpfrontSetl, A.CDPublicInfo, A.CDCollReq, A.CDSpreadCurve, A.CDPremium, A.CDOptType, A.CDAccrue, A.CDRefPrice, A.CDPremiumAmnt, A.CDLastCoupLength, A.CDWhoDelivers, A.CDCollateralText, A.CDFactorReason, A.CDDefStartProt, A.CDDefEndProt, A.CDDefProtType, B.CDComment, A.CDEvent, A.CDCurveType, A.CrvShName, A.CDRefEntity, A.CDRefIndustry, A.CDRefCountry, A.CDRefSNP, A.CDRefMoody, A.CDRefMSRating, A.CDRefId from TMP_credDerivOrig A, C1_credDerivComment B where A.CDId = B.CDId; rows affected: 566606 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of P Kishor Sent: Wednesday, February 07, 2007 5:39 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] What does this mean??? On 2/7/07, Anderson, James H (IT) <[EMAIL PROTECTED]> wrote: > not an error(21) at dbdimp.c line 398 > > I'm using DBD::SQLite and got this error. What does it mean and how best > to hanle it? > well, how about some context? What is the structure of the table(s) you are querying, what is the query, the relevant code snippet, something to go on? The error string itself means that you did something via Perl that violated whatever it was at line 398 of the c program dbdimp.c. -- Puneet Kishor http://punkish.eidesis.org/ Nelson Inst. for Env. Studies, UW-Madison http://www.nelson.wisc.edu/ Open Source Geospatial Foundation http://www.osgeo.org/education/ - collaborate, communicate, compete = - To unsubscribe, send email to [EMAIL PROTECTED] - NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error.
Re: [sqlite] What does this mean???
On 2/7/07, Anderson, James H (IT) <[EMAIL PROTECTED]> wrote: not an error(21) at dbdimp.c line 398 I'm using DBD::SQLite and got this error. What does it mean and how best to hanle it? well, how about some context? What is the structure of the table(s) you are querying, what is the query, the relevant code snippet, something to go on? The error string itself means that you did something via Perl that violated whatever it was at line 398 of the c program dbdimp.c. -- Puneet Kishor http://punkish.eidesis.org/ Nelson Inst. for Env. Studies, UW-Madison http://www.nelson.wisc.edu/ Open Source Geospatial Foundation http://www.osgeo.org/education/ - collaborate, communicate, compete = - To unsubscribe, send email to [EMAIL PROTECTED] -
