Byte order of non-geometry bind/define buffers
mateusz at loskot.net
Mon Sep 4 13:58:18 EDT 2006
I can't find where FDO applies bytes order conversion between
client/server to non-geometry bind and define buffers.
I searched through Rdbi drivers/Gdbi and higher abstractions,
but I can't find it. Get* members of GdbiQueryResult class
use memcpy() function to retrieve data from column buffers.
That's all I see, am I correct?
For example, when I pass pointer to int buffer to bind,
how MySQL/Rdbi/FDO deals with endianness?
Thanks in advance for exaplanation.
More information about the Fdo-internals