Michael, If I extend the Param system to depend on the memory being allocated by the caller of the SetData and that the memory will be there for the duration of the SQL operation then all we need to do is have a pointer to the memory, the size of the memory, and the kind of memory. With these three things we can read/write as needed. The present system is using a Variant data and contains a copy of the initial data that was passed during the SetData.
Eventyally, we could remove the variant and use the getmem method if the TParm is in copy mode and the component would be entirely Variant free. > > In my ideal world, the TParam would not need variants at all. > The problem is that it must store all kinds of data. Implementing > this would mean effectively re-implementing many FVariant mechanisms, > such as conversions from one type to another. > > I'm not quite sure that I understand what you hope to gain with this > new proposed field and parameter ? > > Michael. > > _______________________________________________ > fpc-pascal maillist - fpc-pas...@lists.freepascal.org > http://lists.freepascal.org/mailman/listinfo/fpc-pascal > _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
