Marko Ristola <[EMAIL PROTECTED]> writes:
> I don't know the reason, but that seems to be the problem, that I have
> found.
> isql crashes under conninfo_parse() on line "free(buf)".
In my experience, this is probably a symptom of some code scribbling
past the end of a malloc'd chunk of memory.
"Dave Page" writes:
> Forwarded to -bugs in case it gets missed.
> This looks like it might be an issue to me, though I may well have
> overlooked something in my brief look at the code.
There's nothing wrong with that code. The only modifiable values in the
record are the "val" pointers, which
Forwarded to -bugs in case it gets missed.
This looks like it might be an issue to me, though I may well have
overlooked something in my brief look at the code.
Regards, Dave
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Marko Ristola
> Sent: 0
I'm not sure what it means at the ODBC level, since I don't use ODBC. I was
hoping my observations might help you in the right direction anyway.
If you need to stay with ODBC, you might try posting to the ODBC mailing list
rather than the bugs list -- the problem seems to be in the ODBC driver
Hi Kevin, you're right. When i type
pname = '\'Elim\''
in the EOModeler, it works (fetches the right match).
i can even do
pname like '\'Eli*\''
with the right results.
But what this mean in odbc level? (i don't need to add additional quotes for
other odbc data sources)
When query against numerica
It looks like this is being treated on the server as though the statement is:
SELECT t0."pname", t0."person_id"
FROM "person" t0 WHERE t0."pname" = Elim
rather than:
SELECT t0."pname", t0."person_id"
FROM "person" t0 WHERE t0."pname" = 'Elim'
>>> "YL" <[EMAIL PROTECTED]> 08/01/05 1:
Thanks Eric and Kevin for the responses to my post.
My Testing table was
Person (person_id int not null, name varchar(32))
and my query typed in EOModeler is
name = 'Elim'
EOModeler has an interface letting you specify connection method.
There are adaptors (oracle, informix, sybase...) and odbc
Is the column name "Elim" or "elim"? If the former, try putting quotes around
it, as required by the ANSI and ISO standards for mixed case identifiers. Some
database products fail to comply with the standards in this respect.
PostgreSQL comes close, although it treats unquoted identifers as a
On Mon, 1 Aug 2005, Andrus Adamchik wrote:
> Just tested it with build 312 and the original problem went away. Now
> I am seeing a new problem with null BLOBs only:
>
> java.sql.SQLException: ERROR: column "blob_col" is of type bytea but
> expression is of type oid
bytea is not the correct
