Hi,
I have here pending commit on %subj%. I think there's no reason to use
UNICODE_FSS for text columns. The UTF8 is new in FB2 and I think we can use
it without problems.
Any commnets? Can I do a commit?
--
Jiri {x2} Cincura
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
Jiri Cincura avait écrit le 15/11/2006 :
> Hi,
>
> I have here pending commit on %subj%. I think there's no reason to use
> UNICODE_FSS for text columns. The UTF8 is new in FB2 and I think we can use
> it without problems.
>
> Any commnets? Can I do a commit?
I don't know because if you do that
Le roy Arnaud wrote:
> I don't know because if you do that the scripts don't work in Fb1.5 ?
> Maybe create all scripts with a new extension 2.0 ?
I think, BTW, the current version of FbSessionStateStore will not work on FB1.5.
Maybe we should create some brainstorming (users), who is using and w
Hello:
> I think, BTW, the current version of FbSessionStateStore will not work on
> FB1.5.
>
> Maybe we should create some brainstorming (users), who is using and will be
> using providers with FB1.5.
>
If needed we can try to have scripts for both Firebird 1.5 and 2.0 if
they differ only i
Carlos Guzmán Álvarez wrote:
> If needed we can try to have scripts for both Firebird 1.5 and 2.0 if
> they differ only in things like the encoding. ??
Yaeh, good idea.
But at least in FbSessionStateStore we will have problem with index. :(
And maybe we should add indices to other sql script, t
Jiri Cincura vient de nous annoncer :
> Le roy Arnaud wrote:
>> I don't know because if you do that the scripts don't work in Fb1.5 ?
>> Maybe create all scripts with a new extension 2.0 ?
>
> I think, BTW, the current version of FbSessionStateStore will not work on
> FB1.5.
I don't know i never
Le roy Arnaud wrote:
> I don't know i never test it where is the problem ?
>
Teh problem is with the index, of course. :)
There's also some bug in definition and in code, I've already fixed it, I'll
try commit these changes in 2-3 days, after some testing.
--
Jiri {x2} Cincura
http://blog.vyv
Hello:
> Teh problem is with the index, of course. :)
>
> There's also some bug in definition and in code, I've already fixed it, I'll
> try commit these changes in 2-3 days, after some testing.
>
What about left the scripts iwithout using a given character set ??
That way they should be usin
Carlos Guzmán Álvarez wrote:
> What about left the scripts iwithout using a given character set ??
> That way they should be using the default character set of the database.
I don't think, this is a solution. This will bring more than more problems.
I suppose to use this solution.
1. Create sql s
Jiri Cincura wrote:
> I suppose to use this solution.
> 1. Create sql scripts for 1.5 and 2.0 .
> 2. Tune up 1.5 scripts as best as possible with this engine.
> 3. 2.0 script create for 4k pages (at least) and provide a lot of comments
> there to describe more options to increase the speed (i.e. o
>> 2. Tune up 1.5 scripts as best as possible with this engine.
Ok but it's not so simple because the 1.5 engine don't support index on
column that has a size > 252 so it's dificult to tune the script.
So all search on column username, email are not indexed so on big database
the search can b
le roy arnaud wrote:
>
>>> 2. Tune up 1.5 scripts as best as possible with this engine.
>
>
> Ok but it's not so simple because the 1.5 engine don't support index on
> column that has a size > 252 so it's dificult to tune the script.
> So all search on column username, email are not indexed so
12 matches
Mail list logo
