MySql vs Valentina

[Ruslan Zasukhin]

On 8/28/13 9:03 PM, "AC Marketscout" <ac.marketscout at gmail.com> wrote:

Hi,

> We are developing a new application using LiveCode.  One requirement is
> that there is some easy way to alter the underlying DB schema, on-the-fly,
> by an administrator, who can then also immediately use it to make front-end
> changes.  I have heard Valentina supports tight integration with LiveCode
> and that this may be possible.

Yes, this is possible.
Each aspect of db schema can be changed.


> I¹d like to know if this is true, and are there other benefits to using
> Valentina as opposed to something like MySql (which we are also
> considering).
 
To better understand possible benefits of Valentina I advice you review in
5-30 minutes few our articles of such kind in Valentina WIKI
  
<http://www.valentina-db.com/docs/dokuwiki/v5/doku.php?id=valentina:articles
:articles>
 
Short and not complete list:


* speed -- can be times faster of normal row-based dbs (mySQL, SQLite,
postgre, MS SQL, ...)


* smarter -- Valentina Data Model is extended Relational model.

* simpler SQL -- because smarter :)


* mySQL do all via SQL,
 Valentina have this way and API way.

So if you have haer good words about Key/Value DBs, about non-SQL DBs,
Then Valentina is a perfect example of such DB also ..
Valentina is hybrid of many worlds.


* recursive queries

 * SELECT for XML  -> returns ready for use XML..
    todo json


* mySQL is SERVER ... And only.
  SQLite - local engine only

  Valentina have and SERVER and embedded engine ...
  so you have from box working both ways without any headacke.


* Valentina Reports  -- right now we prepare very interesting news and
examples ... 


And so on ... 
Please ask more if you need.


-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]