OTRS.
> Subject: Re: [otrs] Troubles viewing output on Customer
> GUI,MSSQL and charset
>
> Hello again Mike...
>
> > There's one thing to pay attention here: OTRS can cache the results
> > from the database query for a couple of minutes. This means that if
&
Hello again Mike...
> There's one thing to pay attention here: OTRS can cache the
> results from the database query for a couple of minutes. This
> means that if you search for 'jim', change your config and
> again search for 'jim', you'll probably see cached results.
> In that case, the confi
Flavio,
On Tue, Nov 30, 2010 at 3:19 PM, Boniforti Flavio wrote:
> Tried with both of them:
>
> No way to get some *written* output (you took a look at the output shown
> in my first post).
There's one thing to pay attention here: OTRS can cache the results
from the database query for a couple o
Hello Mike,
> No, you should actually include them in the Params section,
> otherwise they're not used.
OK, put them under the "Params", nothing changed...
> Latin1_General is not a character set name, or at least not
> one recognized by Perl's Encode, it's a MS SQL Server Collation name.
> Pl
Flavio,
On Tue, Nov 30, 2010 at 2:25 PM, Boniforti Flavio wrote:
> I've tried inserting the lines you suggested *before* the "Params"
> section, like:
>
> Name => 'Database clienti',
> Module => 'Kernel::System::CustomerUser::DB',
> SourceCharset => 'utf-8',
> DestCh
Hello Mike and thanks for your quick feedback.
> If your remote database is unicode, add this to your mapping.
>
>SourceCharset => 'utf-8',
>DestCharset => 'utf-8',
>
> Actually, I'm not quite sure if DBD::Sybase would also return
> Unicode, you might want to experiment
If your remote database is unicode, add this to your mapping.
SourceCharset => 'utf-8',
DestCharset => 'utf-8',
Actually, I'm not quite sure if DBD::Sybase would also return Unicode,
you might want to experiment with trying either 'utf-8' and
'iso-8859-1' as values for Sourc
Hello everybody.
I'll be starting from the latest problem I'm encountering, which is as
follows: when I do a search in my Customer Database, I get the correct
number of records, but they print out as blank/empty lines (look here:
http://tinyurl.com/2cx44r2 ).
Here the background and the setup:
D