elidorio2,
it wasn't my intention to say we leave you. But we've all our day to day jobs. Actually im bussy with my private work.
possible issues we've to think about concerning this PG exception:
- 1. Is it possible that the pglib.dll 64Bit header has changes and we don't know it?
2. Do we use old integers instead of pointers in our code? Here i've took a look. First impression: No. But still possible.
3. A code snipped from PG9 64 pgtypes_interval.h:
Code: Select all
typedef struct
%u7b
#ifdef HAVE_INT64_TIMESTAMP
int64 time; /* all time units other than months and years */
#else
double time; /* all time units other than months and years */
#endif
long month; /* months and years, after time for alignment */
%u7d interval;
Which means ism is eventually right.
4. Where, when, why happens this access violocation?
5. If the integers are right in the plaindriver definitions than which one (2byte smallint/4byte Integer/ 8byte Int64) is in use for which function? As far as i can see (quick look) uses PostgreSQL only 2 and 4 byte integers. But this could be changed too since 64Bit.
6. Can we keep the olp PG plaindrivers or do we need a new 64Bit one as new protocol.
OR is it a setting problem on your computer.
My problem is that i don't have Windows64 and actually i broke with lazarus for coding because the debugger is to slow and instable (personal oppinion -> FPC is a terific thing!! And i like it.) or i use wrong settings which i don't know. Looking for such an issue blindy and no possibility for tests must going wrong. So it would be better to get help from others like ism.
Things which where helpful to know (Please answer):
Result of: SizeOf(Integer); -> 4 or 8 byte (like in XE2 64Bit here we've to use the NativeInt for 32Bit integer)
Can you access PG in Win32 with the updated sources?
ism,
a hint or more a feeling (blindy typing now) concerning MySQL64: open MySQLResultSet.pas. Look for a function InternalGetString(ColumIndex: Integer): String;
Set a breakpoint there. Is it possible that the PULong incrementing is correct but the PULong size has changed and we point to the midle of nowhere?
elidorio2, On this post you can see how complex your problem is,
Edson and w'll need some time and other users to find out what's going wrong. I wish i could consider you i can do it in a half hour but again i can't test it by my selves.
So be patient, don't overhurry and try to help us to help you.
Best regards,
Michael