Steve,
I don't really understand the internals, but is the integer being
searched in the where clause by chance "xmin"? I believe this is how
the ODBC driver figures out the appropriate row to return to Access - at
the very least it's what appears in linked tables when you enable Row
Versioning...
Also, does the log stuff vary when you use different versions of the driver?
EE
Steve News wrote:
> Joost,
>
> I'm going to jump in here. I work with Michelle, but am having trouble
> posting to the pg list. When we look at the log files, some times we
> see strange things. I don't have them handy to cut and past here, but
> for example, I can request all rows from a table (no "where" clause").
> Then in the log, I may see three queries. The first is correct. Then,
> there are two that on their own have added a where clause that
> restricts the data by saying record_id = {some random big integer
> having nothing to do with nothing}. Then the table opens with every
> dell filled with #delete#.
>
> --steve backman
>
> At 2/15/2005 01:33 PM, you wrote:
>
>> Hi Michelle,
>>
>> Did you look at the log files that the ODBC drivers generates (if
>> turned on) and/or the PostgresQL log files?
>>
>> Groeten,
>>
>> Joost Kraaijeveld
>> Askesis B.V.
>> Molukkenstraat 14
>> 6524NB Nijmegen
>> tel: 024-3888063 / 06-51855277
>> fax: 024-3608416
>> e-mail: J.Kraaijeveld@Askesis.nl
>> web: www.askesis.nl
>>
>> ---------------------------(end of broadcast)---------------------------
>> TIP 8: explain analyze is your friend
>>
>>
>>
>> --
>> No virus found in this incoming message.
>> Checked by AVG Anti-Virus.
>> Version: 7.0.306 / Virus Database: 265.8.8 - Release Date: 2/14/2005
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
>
