Valentina 2.0. -- What is your 3 DREAM features?

[Ruslan Zasukhin]

on 1/31/04 1:56 PM, jda at jda at his.com wrote:

> Yes, that's important to most of us, I think. UTF-8 is the "native"
> language of RB now, so it's much easier to just store and retrieve
> that. Also, Valentina dbs are already large.

I not agree!

On benchmark pages, you can find results
   fileMaker, 4D, V12, NeoAccess, all have had BIGGER dbs than Valentina

And I am sure Valentina has VERY COMPACT data and indexes.
I do not waste any bit.

PRE-ALLOCATED empty space in segments, make Valentina db looks big only
initially.

But in this way works 4D, MS SQL Server and I think other dbs.
It seems mySQL InnoDB and it seems Oracle or Sybase even allocate the whole
e.g. 600MB db file. I have read that one of problem of InnoDB in mySQL is
that IF data eat all this space, there is no way to grow more. As for me,
stupid design.

Valentina pre-allocate ONE segment (2-32KB) forr each file,
But MS SQL server allocate 4 or 8 segments at once.

Again. I am sure that Valentina has the most compact indexes,
And data also.

> I know that a lot of
> that is mapped out space, but nonetheless UTF-16 will certainly
> increase the size of these databases even more.


> For me, as you know, my dream feature is unicode! I think the changes
> in 2.0 look absolutely great, and I know I'll make use of many of
> them. But even if you just added unicode to 1.0 I would have been
> delighted...

Unicode did require from us TOTAL changes in all changes.
This was not easy step.

-- 
Best regards,
Ruslan Zasukhin      [ I feel the need...the need for speed ]
-------------------------------------------------------------
e-mail: ruslan at paradigmasoft.com
web: http://www.paradigmasoft.com

To subscribe to the Valentina mail list go to:
http://lists.macserve.net/mailman/listinfo/valentina
-------------------------------------------------------------