[fpc-pascal] Master Detail relationship in SQLdb

Joost van der Sluis joost at cnoc.nl
Sun Jul 15 01:10:43 CEST 2007

On Sat, 2007-07-14 at 15:32 +0200, Martin Schreiber wrote:
> > So, once more, I propose to 'merge' whatever you need so we can
> develop
> > a decent set of components, suitable for all.
> >
> The most questionable component in FCL-DB is TBufDataset <->
> tmsebufdataset.
> I fear the needs of FCL and MSEgui are too different to let a merge
> be 
> possible. Some needs of MSEgui are out-of-scope of the ordinary FPC
> user and 
> the FPC developers (fast widestrings on all platforms comes into
> mind).

Can you specify those? Maybe we can work something out.

I have a question about the widestrings. I thought that tmsebufdataset
handles all strings as widestrings. But I can't find any reference to
that in the code. It would be silly anyways: from the db-engine you'll
get 8-bytes based strings. And a ftString fields's .asString method will
return a normal ansistring. The same holds for your code.

Is this right? I mean:
1) tmsebufdataset doesn't store all the string-types in it's internal
buffers as widestrings?
2) No conversion from/to widestring takes place?

Only if a field is defined as a nvarchar on the db-engine it is handled
as a widestring? (ftWideString)

Because, then there's actually no difference?


More information about the fpc-pascal mailing list