New releases WITHOUT Unicode

[Thomas Heim]

 Posted by:  Thomas Heim 

Is there a plan to make versions TeamDeveloper and SqlBase without UNICODE?
We realy do NOT NEED this feature. For us it makes only the source code
bigger and kills the performance of the database.

Thomas

[arvindram11]

 Posted by:  Aravind Ram 

We don't need this "Feature" too. Wish there was a way to disable it during
installation or something.

Aravind

[martinenco]

 Posted by:  Enrique Martinenco 

All the customers witht Spanish tongue don't need this feature. The
performance cost to pay for a feature that we don't need and we don't ask
for is unacceptable.
I agree with Aravind that by nice to have a instalation option or some like
that for disable this "enhancement".

Enrique

[Mirko]

 Posted by:  Mirko BONANNO 

Of course, is this was possible, we would definitely choose
not to install UNICODE

[Joachim Engel]

 Posted by:  Joachim Engel 

I would prefer UNICODE-less versions (TD + SB) too!

Kind regards
Joachim Engel.

[RainerE]

 Posted by:  Rainer Ebert 

We do not need UNICODE and really would like to have (or better said need) a
UNICODE-less versions or the option to totally disable UNICODE. Otherwise
what would happen with our 20MB exe file and our 20GB database file?

Regards,
Rainer

[Martin Teetz]

 Posted by:  Martin Teetz 


The next SQLBase release "11.5" will allow you to use Unicode or if you
don't want to use it at all not use it. We understand that there is a
pretty large file size penalty when moving everything to Unicode. So
with SQLBase 11.5 you can continue to do ANSI with your local codepage
as you do today and if you like you can add Unicode columns to your
tables. And only those Unicode columns would use mores space, the
existing char columns not.

For Team Developer you will not have a choice other than using Unicode.
But that should not have huge impacts on you. We handle the Unicode
database access for you. Only some included DLLs might need some extra
handling to convert ANSI strings to Unicode in Team Developer.
Windows itself is all Unicode based, so using Unicode, data exchange
with other Windows apps should be quicker because no Ansi -> Unicode
conversions are taking place.

If you like I can provide you the devcon presentation on TD 5.1 and Unicode.

Martin
Unify

[markus.essmayr]

 Posted by:  Markus Eßmayr 

I definitively welcome the UNICODE feature.
As we have to support western and eastern european character sets, we had
some troubles in the past using the ANSI-TD versions.
I also agree, Windows is nearly 100% "UNICODE inside", so calling Windows
functions from TD by using external functions, or even the calls that the
TD-runtime makes internally (implies that the whole TD-runtime is UNICODE)
prevent us from UNICODE-to-ANSI conversion of every string passed.
So the runtime performance should be increased by this feature.

Max

[Clifford Bass]

 Posted by:  Clifford W. Bass 

Hi All,

I would add that I too am looking forward to a UNICODE version of
SQLBase. I did some testing with SQLBase International, and was really
impressed with the abilities. Unfortunately there were some other issues
that prevented migration to that version. I was especially impressed with
the ability to get it to do locale-specific sorting--including on the fly so
to speak. I have never liked the sorting options in the ANSI versions. As
such, I had to create my own "country" to deal with that. It was an
imperfect fix and caused some other issues. All those hassles can be thrown
out with a UNICODE version.

My $0.02 worth.

Clifford Bass