FreeTDS Development Group

[Frediano Ziglio <freddyz77 AT tin.it>]

Il ven, 2003-01-10 alle 21:54, Steve Langasek ha scritto:
> On Fri, Jan 10, 2003 at 09:18:23PM +0100, Frediano Ziglio wrote:
> > Il ven, 2003-01-10 alle 18:25, Steve Langasek ha scritto:
> > > On Fri, Jan 10, 2003 at 06:15:33PM +0100, ZIGLIO Frediano wrote:
> > > > > > - collation is not supported (on either TDS7 and TDS8)
> 
> > > > > What needs to be done to change this?  I don't understand what
> > > > > client-side support is required for collation.
> 
> > > > Every 8-byte char column can have different encoding ... (one greek, 
> > > > another
> > > > chinese and so on)
> 
> > > This doesn't explain to me why changes are needed on the client side.
> > > Isn't it the *server's* job to handle collation?  Or do we each mean
> > > something different by 'collation'?
> 
> > sql2k return collation doing no conversion. The client must translate
> > between charset. I intend collate info attached to all data returned
> > from sql2k using TDS8. If you return a varchar (not nvarchar) a xvarchar
> > type is returned (tds8 never return varchar, only large varchar, called
> > in FreeTDS xvarchar) with collate info and untranslated.
> 
> I really feel like we're talking past each other, here.  I understand
> "collation" in the sense of the LC_COLLATE env var: that is, a sort
> order.  Isn't this for things like 'SELECT xx,yy FROM zz ORDER BY foo'?
> When would the client need to know details about the collation order?

Mm... we are speaking of different things...
For collation I mean "sql collation", non "c collation"
I spoken of things like

-- think @string as a unicode string...
SELECT CONVERT(VARCHAR(80), @string) COLLATE Greek_bin

sql (sql2k only) return single-byte characters encoded with greek...

freddy77