Skip to Content.
Sympa Menu

freetds - RE: MS SQLServer 2000 and "for xml auto" command

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Chad Enney" <Chad.Enney AT noaa.gov>
  • To: TDS Development Group <freetds AT franklin.oit.unc.edu>
  • Subject: RE: MS SQLServer 2000 and "for xml auto" command
  • Date: Thu, 29 Aug 2002 14:35:11 -0600


If this change gets committed for tonight's snap-shot I'll be happy to try it out in the morning!

Thanks again for everything
chad

Frediano Ziglio wrote:

Il gio, 2002-08-29 alle 18:36, Brian Bruns ha scritto:

tds_process_row() is getting unwieldy. Post 0.60 work should include
streamlining this func. Looks like we can simply test for
column_unicodedata and instead call tds_get_string instead of tds_get_n. I don't have access to SQL Server where i am now to test this. Did you
break the switch out to a separate function?

Brian


I fixed problem with ntext (and some other tsql related).
I not added any function and not simplified tds_process_row.
One reason is to not add possible unseen bugs.
Another is this related to ucs2 coding. I think in next release to
improve two think:
- internalization
- odbc driver
We use for i18n an early conversion method (conversion from ucs2 to byte
charsets just after reading from network). I think best method is a late
conversion (convert just before returning data to client). So we should
mantain ucs2 coding in tds and converting (for example) in cs_convert.
This should solve problem with utf8. Also doing so is possible to change
coding in the middle of the dialog.
This is why I propose to remove unicodedata flag...

freddy77



---
You are currently subscribed to freetds as: [Chad.Enney AT noaa.gov]
To unsubscribe, forward this message to $subst('Email.Unsub')








Archive powered by MHonArc 2.6.24.

Top of Page