yes, one connection per database, any thread needs to access this database
would create its own transaction.
To: firebird-support@yahoogroups.com
From: firebird-support@yahoogroups.com
Date: Wed, 15 Jun 2016 21:38:48 +0200
Subject: Re: [firebird-support] performance issue with firebird 3.0
Hello Hugo,
Friday, June 17, 2016, 9:34:17 AM, you wrote:
> Is there the limitation of 31 bytes for column names in the new FB 3?
31 CHARACTERS - as before - for all SQL identifiers, including column
names. They are stored in UNICODE_FSS (3 bytes each, no options) so
it is actually a maximum
Hello friends.
Is there the limitation of 31 bytes for column names in the new FB 3?
--
Atenciosamente,
Hugo Eyng
16.06.2016 15:30, Stefan Heymann li...@stefanheymann.de [firebird-support]
wrote:
> How can I work with that DE_DE_AI collation you mention? Firebird
> doesn't seem to know it.
According to README.intl you must create it in database using CREATE
COLLATION query. I
hope Adriano can shed more
> UNICODE_AI collation is useless, but DE_DE_AI can work unless Stefan
> needs to keep words in other languages in the same field as well.
That's the point. I don't know what language is used (can be every
European language) and so I'll have to live with that.
How can I work with that DE_DE_AI
16.06.2016 11:33, Dimitry Sibiryakov s...@ibphoenix.com [firebird-support]
wrote:
> unless Tomas need to keep words
Oops, it was Stefan, of course. I'm sorry.
--
WBR, SD.
16.06.2016 11:03, Paul Vinkenoog p...@vinkenoog.nl [firebird-support] wrote:
> That's right. I can't think of any circumstances where you would want
> to consider 'hatten' and 'hätten' the same, for instance. Or Mutter and
> Mütter. Actually, I couldn't think of any German word where this would
>
Hi,
you have right Paul and Stefan
sorry for previous answer - i miss that point
regards,
Karol Bieniaszewski
W dniu 2016-06-16 11:03:25 użytkownik Paul Vinkenoog p...@vinkenoog.nl
[firebird-support] napisał:
Hi Stefan,
> > Also, it is questionable if
Hi Stefan,
> > Also, it is questionable if you should consider a and ä different
> > letters, even in German. See e.g.
> > https://de.wikipedia.org/wiki/Alphabetische_Sortierung
>
> For sorting, treating them as "same" is correct. However, for things
> like comparisons (in a unique key for
Hi,
you use wrong collation
UNICODE_CI is truly case-insensitive. In a search for e.g. 'Apple', it will
also find 'apple', 'APPLE' and 'aPPLe'.
UNICODE_CI_AI is accent-insensitive as well. According to this collation,
'APPEL' equals 'Appèl'.
as you can see UNICODE_CI_AI is accent-insensitive
> Also, it is questionable if you should consider a and ä different
> letters, even in German. See e.g.
> https://de.wikipedia.org/wiki/Alphabetische_Sortierung
For sorting, treating them as "same" is correct. However, for things
like comparisons (in a unique key for example) they are not the
Hello firebird-support@yahoogroups.com!
I am trying to deploy Firebird 3.0 to our customers. Only three small
customers are running on FB3, but all of them have the same problem:
invalid transaction handle (expecting explicit transaction start).
This exception happens on different places which
12 matches
Mail list logo