com, Valentina 2 Windows Foundation Database Suite Announced

Valentina 2 Windows Foundation Database Suite Announced

COMPLETE TOOLS FOR DEVELOPMENT USING ALL MAJOR WINDOWS ENVIRONMENTS

November 30, 2005. Beaverton, Oregon. Leading multi-platform database
vendor Paradigma Software, Inc, makers of the ultra-fast Valentina 2
Office Server, announce next-generation suite of components and a
complete suite of tools for creating and deploying desktop and network
based database solutions on the Windows operating system. These tools
are all based on the Valentina 2 database kernel.

Valentina 2's next generation, object-relational database model
builds on the traditional relational database model much like C++
builds on top of the C language. All that you know from working with
traditional database systems from IBM, Oracle and Microsoft also apply
to Valentina-based development. This robust technology excels at ultra
fast management of millions of records. Valentina 2 utilizes a
revolutionary new abstraction data model: Links. Links are highly
sophisticated structures that manage high speed, low overhead handling
of 1:1, 1:M, M:M relationships. Valentina Links include ObjectPtrs and
Binary Links, new reinterpretations of Foreign Keys. A Valentina 2
kernel document on this system is available by free download on the
Paradigma Software website.

Valentina 2 Windows Foundation is a special version of Valentina
Developer's Network. With VDN (Windows Foundation), developers can
develop and deploy complete client-server database solutions to their
customers, royalty free, based on Valentina Embedded Server. Valentina
2 technology also supports XML data/schema management, best practices
Unicode for international applications, Valentina SQL, 448-bit
encryption, transparent file format support across operating systems
and many more features.

Valentina 2 Windows Foundation includes Valentina 2 C++ ADK Standard
Edition for Windows (available separately for $199), and Valentina
Studio Admin Edition for setting up, server start up and monitoring and
other database creation and management utility functions.

Also included in Windows Foundation (and available separately) are:

Valentina 2 COM ADK. High performance COM component for building
desktop database applications with COM-compatible tools such as Borland
Delphi and Microsoft Visual BASIC 6 (and earlier). Valentina 2 COM
means you don't have to use yesterday's database to ensure
compatibility with your existing infrastructure. Valentina 2 COM is
also available separately for $199.

Valentina 2.NET ADK. Valentina 2.NET ADK empowers developers to deploy
enterprise-ready, database enabled desktop solutions with any language
compliant to the Microsoft .NET CLR. The current beta works with
Framework 1.1, while the final shipping release will support Framework
2.0. Valentina 2.NET ADK is also available separately for $199.

Both ADKs include Data Client components for simultaneously querying
both local databases and remote database servers, including Valentina
Office Server.

VDN (Windows Foundation) also allows developers access to two years of
software maintenance, test copies of Valentina Office Server, reseller
pricing on Valentina Office Server and special promotion opportunities.
VDN (Windows Foundation) pricing starts at $599, with support options
in multiple languages.

For more information, visit the Paradigma Software website at
http://www.paradigmasoft.com.

About Paradigma Software, Inc

Founded in 1998, Beaverton, Oregon-based Paradigma Software, Inc is the
leading provider of incredibly fast and robust database solutions for
business and development. Valentina 2 technology powers solutions as
diverse as graphics applications from major Japanese electronics
companies to solutions supporting US public schools. Paradigma Software
solutions are available for every major development environment on the
Windows and Macintosh platforms.

Contact

Paradigma Software
Ph. (503) 574-2776
http://www.paradigmasoft.com

Links? Hierarchical DBMS were superceded by RDBMS some 30 years ago.

cheers,
</wqw>

Hi Vlad,

* Hierarchical dbs wa snot best. Network dbs was more flexiable.
* Yes RDBMS have win 30 years ago, but why? Do you remember good
reasons why?

One of the killer-reasons was the SQL. Network and Hierarchical dbs did
not
get such powerful tool, which allow easy query a remote server, as well
as
give a way to developer fast do/change query wiout codding/recompiling.
This is what books says...Also books says that Network dbs was in
average
4-5 times faster

To get you better feeling, let me note, that Valentina adds the
abstraction
LINK as on API level so on SQL level.

From Valentina Data Model point of view, the FOREIGN KEY which you use
IS
also LINK. Not just a constraint as SQL describe it.

And the main: Valentina introduces 2 new kinds of links: ObjectPtr and
BinaryLink. Both can be used in low level API (C++/C#/VB.NET) so in SQL.
Benefits are described in Valentina Kernel.pdf

Important to hear next point: Valentina support Relational model AND
extend
it by new Object-Relational features. So be sure this is NOT in any way
hierarchical model. Let me know if you have more questions.


*** Sent via Developersdex http://www.developersdex.com ***

Hi Vlad,

* Hierarchical dbs wa snot best. Network dbs was more flexiable.
* Yes RDBMS have win 30 years ago, but why? Do you remember good
reasons why?

One of the killer-reasons was the SQL. Network and Hierarchical dbs did
not
get such powerful tool, which allow easy query a remote server, as well
as
give a way to developer fast do/change query wiout codding/recompiling.
This is what books says...Also books says that Network dbs was in
average
4-5 times faster

To get you better feeling, let me note, that Valentina adds the
abstraction
LINK as on API level so on SQL level.

From Valentina Data Model point of view, the FOREIGN KEY which you use
IS
also LINK. Not just a constraint as SQL describe it.

And the main: Valentina introduces 2 new kinds of links: ObjectPtr and
BinaryLink. Both can be used in low level API (C++/C#/VB.NET) so in SQL.
Benefits are described in Valentina Kernel.pdf

Important to hear point: Valentina support full Relational data model
and SQL
plus it extends it by new abstractions and features to get
Object-Relational
model.

Valentina is NOT hierarchical and NOT network database.
Valentina is Object-Relational database.


*** Sent via Developersdex http://www.developersdex.com ***

you may find this article educational: ON WHY NOT POINTERS
< http://www.dbdebunk.com/page/page/2715232.htm> ;

[quote]
Date has written a number of articles explaining the problems of using
pointers rather than "values" to link related information.
[/quote]

cheers,
</wqw>

Hi Vlad,

Thank you for URL. Actually I have a lots of books on database design
and
development, so unlikely I will read something new.

So, I have go by URL and I have found almost nothing there. Some
question
and some answer. Answer point to [The Final NULL in the Coffin]. Here
are
arguments against?

Vlad, you self can give at least one strong, killer argument against
"pointers" ?
Then we can discuss that. May be in new thread.


In any case, Vlad.

* I also like and prefer relational model. This is why I do NOT like OO
DBMS
and their ideas. I prefer Extend relational model.

* Valentina have not just pointers, but new abstraction of data model --
LINKs. Again, Valentina Model naturally transform Foreign Key into links
also.

* I want ensure you that Valentina Links very differ from what you could
see
in hierarchical dbs (if you did). We have for example some developers
in
former dbVista developers. They say that Valentina offer a lots of
features
that dbVista did not have.

But again and again, Valentina is not analog of dbVista. or other
network
model. Please note: Valentina is like C++. C developers could use
everything
they did know to develop now projects and step by step learn and use new
features. Valentina DB is analog of e.g. mySQL or even more correct --
Postgre, since Postgre also moves into Object-Relational direction.

I again want to say that Links of Valentina do THE SAME tasks as Foreign
Keys
do, but in MORE effective way:
- they can use less disks space (a lots less)
- they are faster. Joins on ObjectPtr is faster several times of join
on FK with
long ID and long PTR fields.
- They are simpler in use.
- they give you more clean database structure.
- ...

Also I can note, that many developers which port databases from e.g
mySQL
or Access start switch FK-link to ObjectPtr-link to get benefits. Also
it is good
that Valentina offer simple refactoring SQL and API command, which allow
convert RDB link into ObjectPtr.

Example. If you have tables with million and e.g. 5 million records,
then
conversion to ObjectPtr link reduce db size on
first table 1 + 12 = 13 MB
second table 5 + 60 = 65 Mb (if it have own key)

Prove me that such huge saving in disk size are bad!

Less disk size automatically means higher speed, because less disk i/o
operations. Because more effective caching. But this is only one part of
why
ObjectPtr faster.

Hmm, this text mainly is about ObjectPtr. This feature was in Valentina
v1.
Developers use it about 7 years already.

But the most exciting feature of Valentina 2 is Binary Link. Just a
dream. :-)
We still actively develop it and increase its effectiveness.

*** Sent via Developersdex http://www.developersdex.com ***