michel.weber
Posts: 256 Joined: Sat Oct 08, 2005 12:40 pm
Post
by michel.weber » Wed Jul 26, 2006 10:09 am
Hi
I have tried to make the DB Walker on our appliance work with SQLServer databases.
Everything works fine, except a field of type text returns the following : net.sourceforge.jtds.jdbc.ClobImpl@6f9b8e
net.sourceforge.jtds.jdbc.ClobImpl@2bd3a
etc. What am i doing wrong?
jason112
Site Admin
Posts: 347 Joined: Tue Oct 26, 2004 5:35 pm
Post
by jason112 » Wed Jul 26, 2006 11:05 am
Is it only one text field returning that, or do all?
Are there any unusual settings for that field, encodings, etc?
michel.weber
Posts: 256 Joined: Sat Oct 08, 2005 12:40 pm
Post
by michel.weber » Thu Jul 27, 2006 3:56 pm
There is only one field of type text in the table all the others are varchar or date.
I'm not sure what unusual settings could be, here is the table definition
CREATE TABLE [dbo].[NewsTraduites](
[NewsTraduiteID] [int] IDENTITY(1,1) NOT NULL,
[NewsID] [int] NULL,
[LangueID] [int] NULL,
[Titre] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[Texte] [text] COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[LienPrincipalURL] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[ImageLegende] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL CONSTRAINT [DF_NewsTradui_ImageLegend1__20] DEFAULT (' '),
[EstSynchrone] [bit] NOT NULL CONSTRAINT [DF_NewsTradui_EstSynchro_4__14] DEFAULT (1),
[LiensSynchrones] [bit] NOT NULL CONSTRAINT [DF_NewsTradui_EstSynchro_5__14] DEFAULT (0),
[LiensTraduits] [bit] NOT NULL CONSTRAINT [DF_NewsTradui_EstSynchro_6__14] DEFAULT (0),
CONSTRAINT [PK_NewsTraduites_1__14] PRIMARY KEY CLUSTERED
michel.weber
Posts: 256 Joined: Sat Oct 08, 2005 12:40 pm
Post
by michel.weber » Sun Aug 06, 2006 8:21 am
HI
Any help with this?
jason112
Site Admin
Posts: 347 Joined: Tue Oct 26, 2004 5:35 pm
Post
by jason112 » Mon Aug 07, 2006 10:39 am
Yes, sorry about the wait. We will have a DBWalker update
coming out that should fix this, we'll let you know when
it's available.
jason112
Site Admin
Posts: 347 Joined: Tue Oct 26, 2004 5:35 pm
Post
by jason112 » Wed Aug 09, 2006 12:53 pm
The DBWalker 1.3.5 update is available for download and should fix this issue. Let us know if you have any problems or questions.
michel.weber
Posts: 256 Joined: Sat Oct 08, 2005 12:40 pm
Post
by michel.weber » Thu Aug 24, 2006 7:49 am
Just to let you know that the last update fixed the problem.