Flexibility is the compelling hallmark of the Valentina programming interface. SQL-purists can code entirely in SQL; Code-skittish designers can build an entire database with the VS GUI app; Speed-demons can surpass many SQL performance limitations and use efficient set theoretic functions for accelerating many simple queries; Object oriented enthusiasts can use and build upon the language-specific class interfaces to expand the interface in powerful ways that offer even greater performance and storage improvements; And efficiency aficionados such as myself, who share the Valentina Author's compelling "need for speed", can combine all of the above techniques as appropriate to achieve a truly stellar level of performance and compactness.

Power in programming, as in all endeavors, comes from choosing the best tool for the job at hand. Valentina's Power is based in the large number of tools it provides. The ability to transparently switch between in-memory, local-disk based, and client/server implementations for a database is wonderful. I take full advantage of foreign-key, object-pointer, and binary-link relationships to optimize structures for expected high-volume usage patterns. I have added hash-encoding fields, I have created custom field accessor classes that transparently execute a simple SQL query only upon need, I have implement genetic search algorithms. And I relish both the inherent flexibility that Valentina offers me to perform optimizations such as these as well as the incredibly fine technical support that assists me in figuring out how to do so.

- Ed Kleban on Valentina for REALbasic