[cvsnt] Re: Help with Audit

[Clovis Garcia]

Bo,


I did the same you said. I used the CVSNT panel to enable the plugin and 
filled the boxes with the information required. Nothing has been done 
manually but I´ve checked that the Message and Diff columns were defined 
as text. I´ve changed it now but the Directory column was already 
defined as nvarchar and the problem was happening with it too.

I did a trace to check the commands sent to the database by CVSNT and 
noted that the messages was already sent with the errors.

If there is another thing to check let me know, but I say in advance 
that I just enabled the plugin, filled the boxes and continued to use 
the CVS normally.

Regards,
Clóvis



On 15/2/2006 05:48, Bo Berglund wrote:
> Are you really sure that ODBC is used for MSSQL/MSDE?
> When I set this plugin up I do not create an ODBC entry, I just 
> enter the login data directly in the boxes...
> 
> Looks to me that you might be using ADO for the MSSQL database 
> engine, or are you creating the ODBC entry automatically in the 
> background? 
> 
> Concerning unicode storage in MSSQL database tables:
> 
> 1. The tables *must* be defined as holding nvarchar or ntext data.
>    If I look in my copy of create_tables_mssql.sql I see that all
>    text columns are just plain text, not ntext as they should be.
>    That's the Message and Diff columns.
> 
> 2. When sending a query to insert or update the columns with text
>    data the actual string must be preceded by N as in:
>    UPDATE CommitLog SET Message = N'text data goes here' WHERE bla bla
>    And of course any single quote ' inside the message itself has
>    to be doubled to not cause an SQL problem
> 
> 
> Best regards,
> 
> Bo Berglund
> 
> 
> -----Original Message-----
> From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf
> Of Tony Hoyle
> Sent: den 14 februari 2006 23:45
> To: cvsnt at cvsnt.org
> Subject: [cvsnt] Re: Help with Audit
> 
> Bo Berglund wrote:
>> Tony,
>> which sourcefile is used to fill the commitlog database entries?
>> Are you using ADO to access the MSSQL database or some other means?
>>
> ODBC, using unicode to send it to the database (so should be universal).
> 
> It's possible your database isn't configured to store the extra 
> characters... can't remember what I did last time to store foreign 
> characters in MSSQL.
> 
> Tony
> _______________________________________________
> cvsnt mailing list
> cvsnt at cvsnt.org
> http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt