freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
Re: [freetds] Wildcard selection leads to data mangling
- From: "Lowden, James K" <james.k.lowden AT alliancebernstein.com>
- To: "FreeTDS Development Group" <freetds AT lists.ibiblio.org>
- Subject: Re: [freetds] Wildcard selection leads to data mangling
- Date: Tue, 13 Mar 2007 10:29:47 -0400
> From: Sherrill, Justin
> Sent: Tuesday, March 13, 2007 8:30 AM
>
> I'll see data missing from a given cell and replaced with data from
> other cells. For instance, a cell (tuple?) that is supposed to
> contain a serial number that is a 16-char mix of letters and numbers
> will instead contain the last 3 characters of a later datetime
> field and the MAC address in the next cell over.
>
> 300013544623AD32 -> 7AM00:07:42:00:CD:3A
>
> I've now noticed that sometimes I just don't seem to be able to
> retrieve data:
>
> # echo 'select count(*) from table1' | /usr/bin/bsqldb -q -S sqldb
> -U username -P password -D mydb
> 24983
>
> # echo 'select * from table1' | /usr/bin/bsqldb -q -S sqldb -U
> username -P password -D mydb *** glibc detected *** double free or
> corruption (out): 0x091aae68 *** Aborted
I've seen that before. I don't remember why and I'm sure it's been
fixed. One solution might be to use a recent snapshot.
It's not a matter of the SQL text using '*' or not. It's a matter of
memory management for some datatype.
I found a discussion around 4/18/2006 ("*** glibc detected *** double
free or corruption") on this list that led to a patch from Frediano. I
would think whatever was in that patch was incorporated in 0.64 when it
was released.
There have also been some corrections to bsqldb since its release. Does
tsql do the same thing? It's perfectly safe to download the current
bsqldb into your extracted 0.64 tree and rebuild.
HTH.
--jkl
-----------------------------------------
The information contained in this transmission may be privileged and
confidential and is intended only for the use of the person(s) named
above. If you are not the intended recipient, or an employee or agent
responsible
for delivering this message to the intended recipient, any review,
dissemination,
distribution or duplication of this communication is strictly prohibited. If
you are
not the intended recipient, please contact the sender immediately by reply
and destroy all copies of the original message. Please note that we do not
accept
account orders and/or instructions by e-mail, and therefore will not be
responsible
for carrying out such orders and/or instructions. If you, as the intended
recipient
of this message, the purpose of which is to inform and update our clients,
prospects
and consultants of developments relating to our services and products, would
not
like to receive further e-mail correspondence from the sender, please "reply"
to the
sender indicating your wishes. In the U.S.: 1345 Avenue of the Americas, New
York,
NY 10105.
-
[freetds] Wildcard selection leads to data mangling,
Sherrill, Justin, 03/12/2007
-
Re: [freetds] Wildcard selection leads to data mangling,
ZIGLIO, Frediano, VF-IT, 03/13/2007
- Re: [freetds] Wildcard selection leads to data mangling, Sherrill, Justin, 03/13/2007
- <Possible follow-up(s)>
- Re: [freetds] Wildcard selection leads to data mangling, Lowden, James K, 03/13/2007
-
Re: [freetds] Wildcard selection leads to data mangling,
ZIGLIO, Frediano, VF-IT, 03/13/2007
Archive powered by MHonArc 2.6.24.