Unknown marker and ntext fields
camber at umcc.ais.org
Tue Dec 14 08:15:16 EST 1999
Oops, that should have read "ddl", as in your table create statement. typos!
The TDS 7.0 support is very new, so there are likely to still be quirks
with it. Currently the behaviour with unicode fields is to strip them back
down to ascii. The next step will be to allow the client to specify
whether it wants unicode or ascii returned when binding. Running the
client at 4.2 should make the ntext fields come back as text fields.
Is there a reason that you need ntext instead of text fields? If not, I
would recommend running the client at 4.2 at least for now.
On Tue, 14 Dec 1999, lee Jackson wrote:
> I'm using TDS 7.0 ( or at least that's what I specified when I configured ).
> Is there a way to check??
> I'm not quite sure what you mean about the dll for the table...could you
> clarify please?
> I've got around this by using a plain old text field for the data which I
> can do at the moment ( parts of our system are on line commercially ,
> luckily Unicode support isn't eheh), but it is a temporary solution. I was
> wondering if I might have to build freetds differently in order to allow
> access to Unicode fields....?
> Sorry fumbling about in the dark a little here.
> Thanks for the response Brian.
> Lee Jackson
> City Mutual
> -----Original Message-----
> From: bounce-freetds-97225 at franklin.oit.unc.edu
> [mailto:bounce-freetds-97225 at franklin.oit.unc.edu]On Behalf Of Brian
> Sent: 11/12/1999 00:13
> To: TDS Development Group
> Subject: [freetds] Re: Unknown marker and ntext fields
> Can you send the dll fo rthe table you are using? Also, are you using TDS
> 4.2 or 7.0?
> On Fri, 10 Dec 1999, lee jackson wrote:
> > Ive been modifying the dbtest code in order to test the functionality of
> > freetds. Finally get it to connect and query....was very hopeful that my
> > linux to MS SQL 7.0 problems where solved. However I have a table with an
> > ntext field that I need to both query, insert and update. However whenever
> > I retrieve a dataset with a *populated* ntext field present I get a long
> > list of Unknown Marker messages ( usually a message with 0!! and then
> > another message with a different number ). Well I know that MS SQL 7.0 and
> > FreeTDS have problems so this was expected. But I do need to get this
> > working, somehow......
> > Can anyone suggest things for me to try to get this working? Is this a
> > known problem and is there an ETA on a bug fix?
> > Many thanks
> > Lee Jackson
> > City Mutual Ltd
More information about the FreeTDS