[SqueakDBX] MSSQL, selecting nvarchar (other types too) field
Mariano Martinez Peck
marianopeck at gmail.com
Fri Apr 29 14:14:45 UTC 2011
On Fri, Apr 29, 2011 at 3:53 PM, Miguel Sanchez <mikey.sanchez at gmail.com>wrote:
> OK thanks guys I'll answer answer both in one shot.
> > Date: Fri, 29 Apr 2011 10:54:37 +0200
> > From: Mariano Martinez Peck <marianopeck at gmail.com>
> > Subject: Re: [SqueakDBX] MSSQL, selecting nvarchar (other types too)
> > field causes DBXTypeNotSupported.
> > To: The complete and open-source solution to relational database
> > access <squeakdbx at lists.squeakfoundation.org>
> > Message-ID: <BANLkTi=jeTSo2UOvchsyc=Mp=WbRtfRVxw at mail.gmail.com>
> > Content-Type: text/plain; charset="iso-8859-1"
> > Hi Miguel. This is something that we really need to fix and make it
> My apologies for the newbie questions and generally being dense about
> understanding the code.
your questions are very welcome.
> > I will try to explain: OpenDBX library have 4 special functions (check
> > above in http://www.linuxnetworks.de/doc/index.php/OpenDBX/C_API/1.2)
> > managing large objects WHEN the backend requires such.
> > We wrongly understood that at the beginning. So...we throw
> > DBXTypeNotSupported for every large object even if we could really
> > it.
> .... and this includes nvarchar? This doesn't need the large object
> functiuon calls does it? doesn't really matter. If it's assigned
> unknown then it needs to be handled anyway.
grrrr sorry my bad. I got confused about large objects...
OpenDBX has a list of supported types, that you can check here:
nvarchar is not even mentioned there :(
So I guess it is not supported. But as said, try it overwritting
createDataTypesMap. And tell us what happens.
If it doesn't work, we can ask Norbert (OpenDBX developer) since he is
always very helpful.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SqueakDBX