--- In firebird-support@yahoogroups.com, Mark Rotteveel wrote:
> The Firebird wire protocol does not perform well over higher latency
> connections, like over the internet.
>
> Also, are you implying that your server is directly open and available
> on the internet? You might want to consider
I have had Firebird installed on the Linux server that serves my website, which
has good speeds, and I have good up and download speeds in my Internet
connection from my fast home computer (Windows 7).
However, when I connect using isql on my home computer to a DB I have put on
that Linux serve
OK, I gave up and wrote my own UDF. It ended up having exactly the same problem
as the one in FreeUDFLib, namely that if the first character, which gets copied
directly into the result string, is accented, you get "Malformed String" when
it is returned.
This is despite the fact that in my first
I just solved my own problem, and wanted to help anyone else with the same
problem!
I'm trying to write a UDF that returns memory allocated with ib_util_malloc,
that can be freed with the FREE_IT directive.
I #included ib_util.h (after ibase.h), and added ib_util_ms.lib as an
additional depend
nn Harrison wrote:
>
> On Fri, Jun 1, 2012 at 12:20 PM, dancooperstock wrote:
>
> >
> > Second, the following also fails with "Malformed String":
> >
> > SELECT f_GenerateSndxIndex(column) FROM table ORDER BY 1
> >
> > If I omit the ORDER BY
Michael, the character set is set to UTF8. Frankly I think this is most likely
a bug/weakness in the UDF.
--- In firebird-support@yahoogroups.com, Michael Ludwig wrote:
>
> dancooperstock schrieb am 01.06.2012 um 16:27 (-):
> > I can force the error with just this SQL:
>
OK, did some more experimentation. I can force the error with just this SQL:
SELECT f_GenerateSndxIndex('ÉLISE') FROM rdb$database
Two small follow-up points. First, I'm using FB version 2.0.3.
Second, the following also fails with "Malformed String":
SELECT f_GenerateSndxIndex(column) FROM table ORDER BY 1
If I omit the ORDER BY, it works fine.
Also, for data without accents, it works fine.
I have a DB from a user of my software, with a lot of accented (French)
characters in it. The character set is UTF8.
When I do:
SELECT DISTINCT f_GenerateSndxIndex(column) FROM table
I get a "Malformed String" error.
However, doing that select without DISTINCT, or without the f_GenerateSndxInd
