Which DB system to choose?

The book is worth to be read!

MariaDB is the Free as in Beer/Free as in Speach version of MySQL that doesnt need a special license for commerical use. Most linux distros have switched over to it. If not, most have it in their repos to be installed in place of MySQL.

Maria at least as screwed up as mySQL was with the dual license
https://mariadb.com/kb/en/mariadb/licensing-faq/

That said why people bother with this ambiguity astounds me
PostgreSQL is free free free as in ANYTHING you want to do with it free
http://www.postgresql.org/about/licence/
The relevant piece
[/i]Permission to use, copy, modify, and distribute this software and its documentation[/i] for any purpose, without fee, and without a written agreement is hereby granted, provided that the above copyright notice and this paragraph and the following two paragraphs appear in all copies.

Save yourself the trouble of having to figure out whether you need to contribute your code back or not , buy a license or not.
Use Postgresql (which is still a far more capable DB as well IMHO)

[quote=247650:@Norman Palardy]Maria at least as screwed up as mySQL was with the dual license
https://mariadb.com/kb/en/mariadb/licensing-faq/

That said why people bother with this ambiguity astounds me
PostgreSQL is free free free as in ANYTHING you want to do with it free
http://www.postgresql.org/about/licence/
The relevant piece
[/i]Permission to use, copy, modify, and distribute this software and its documentation[/i] for any purpose, without fee, and without a written agreement is hereby granted, provided that the above copyright notice and this paragraph and the following two paragraphs appear in all copies.

Save yourself the trouble of having to figure out whether you need to contribute your code back or not , buy a license or not.
Use Postgresql (which is still a far more capable DB as well IMHO)[/quote]

Well that is a change in their licensing… as it was a single licence that anyone could use it for anything but the database itself stayed GPL (or whatever OSS license it had).

As for why use it (or MySQL)? there are lots of apps that use MySQL (or derivatives) that dont have an option to use PostgreSQL. Until recent years, PostgreSQL was a PITA to setup, and use. I agree in recent years it has become much better in the install/configure.

For instace, WordPress blogging software requires MySQL and doesnt work with PostgreSQL (or it didnt as of 6-7 months ago). So if you want to use one of the most widely used blogging software, you use MySQL (or derivatives).

I am not arguing that MySQL is better. But there are some use cases where it is your choice or your only choice.

[quote=247658:@scott boss]Well that is a change in their licensing… as it was a single licence that anyone could use it for anything but the database itself stayed GPL (or whatever OSS license it had).
[/quote]
I’ve never known it to be radically different than mysql’s but can’t say I have an old copy anywhere to point at

[quote=247658:@scott boss]As for why use it (or MySQL)? there are lots of apps that use MySQL (or derivatives) that dont have an option to use PostgreSQL. Until recent years, PostgreSQL was a PITA to setup, and use. I agree in recent years it has become much better in the install/configure.

For instance, WordPress blogging software requires MySQL and doesnt work with PostgreSQL (or it didnt as of 6-7 months ago). So if you want to use one of the most widely used blogging software, you use MySQL (or derivatives).

I am not arguing that MySQL is better. But there are some use cases where it is your choice or your only choice.[/quote]
And therein lies the rub
A fair number of these projects started out with mySQL as “Hey its free” which has almost always been a misunderstanding - perhaps not if you go all the way back to 1996 / 1997
But its been dual licensed for so long and only since Oracle bought mySQL AB has it become a real sticking point as people get sued or strong armed into buying a license for a “free” product (which it isn’t always under the terms of the dual license)

PostgreSQL has been a PITA to deploy until much more recently. Not denying that.
But the sudden realization that mySQL might actually cost you a lot of money has made a lot more people very aware of this.
Unfortunately there are still projects, like Wordpress, where using it could force you into buying a pricey license.
And then you either replace Wordpress or pony up the $ because they used a “free” database.

For me, if it comes to using blogging software for commercial purposes, I might just find something other than Wordpress regardless of how popular it is. Its not the only game in town.

[quote=246990:@Markus Winter]To save Raphael the work:

Valentina Embedded royalty free server:

5 concurrent connections: $600
10 concurrent connections: $3000[/quote]

Somethings are missing. The SQLite portion gives you more connections:

5 Connections for Reports / REST / Valentina DB & 10 Connections of SQLite $599.99
10 Connections for Reports / REST / Valentina DB & 25 Connections of SQLite $2999.99

Also note that it incorporates our Reports Server as well, and not just database stuff.

[quote=246990:@Markus Winter]To save Raphael the work:

Valentina Embedded royalty free server:

5 concurrent connections: $600
10 concurrent connections: $3000[/quote]

Lynn already have show that this text is not accurate. Since here question is about SQLite Server then compare:

Valentina Server VDN (Embedded)… cubeSQL (Redistributable License)

10 SQLite connections + 5 Valentina’s $599
… Up to 5 concurrent connections: $1500/year.
25 SQLite connections + 10 Valentina’s $2999… Up to 10 concurrent connections: $3000/year.

To start with cubeSQL Redistributable, you need $1500 and you get 5 SQLite connections.

To start with Valentina Embedded Server, you need $599 and you get 10 SQLite connections AND

  • 5 Valentina DB connections in the same server
  • 5 Valentina Report connections in the same server
  • MAIL server
  • PRINTING on 3 OS (v6.3+)
  • REST API – connect to your SQLite or Valentina DBs or Reports from e.g. Android or WinOS or …

You can start with existing SQLite database really in few seconds. In case SQLite power will not enough - you can put some/all data into Valentina tables with vertical storage, which are magnitude faster.

And of course Report Server - is killer feature. Get it. Use it ))

Hi Ruslan,

[quote=248283:@Ruslan Zasukhin]+ REST API – connect to your SQLite or Valentina DBs or Reports from e.g. Android or WinOS or … [/quote]Did you implement this feature request? If not do you plan to?

Hi Steve,

please check in the thread you point by URL :
you have asked 11 July, and at 20 July I have answer:

as promised :slight_smile:

Into Valentina GIT made commit from our developer about improvement of REST API as you suggested:

Execute query once:
“Params”: [1, “Smith”, null]

Execute query twice:
“Params”: [ [1, “Smith”, null], [2, “Ivanov”, null] ]
Today later we will produce 6.0 b24 where this will be available.

[quote=248297:@Ruslan Zasukhin]Hi Steve,

please check in the thread you point by URL :
you have asked 11 July, and at 20 July I have answer:

as promised :)[/quote]
Erm… how did I miss that?

Thanks, Ruslan.

I would like to point out that Christian has done a superb job on the MBS SQL plugin. Now, prepared statements (practically mandatory now in a web app) are fully compatible with those of Xojo.

Therefore, we have no need to rewrite all these methods (When we move to the SQL plugin). Ditto for the methods of recordset: recordcount, moveFirst etc.

The switch to the plugin is very easy now. The enormous advantage of this plugin is that it relies on a very reliable library (SQLAPI++), designed by pros of SQL. And do not forget the support of Christian!

We have create 5 min video, which demonstrate how you can in 3-5 minutes convert
EXISTING Xojo project with local SQLite database, into project that is able work with Valentina SQLite Server.

As simple as 10-12 lines of code only typed in 3-5 minutes.
Most new code similar to any DB Server: specify host, user, password, connect.

https://www.youtube.com/watch?v=dlbTIN2WyRE&feature=youtu.be

If you prefer read text, you can read the same tutorial in WIKI:

Looks great but when watching the video I got so distracted by the background music that I ended up doing searches for episodes of Tommy Cooper and Benny Hill.

You can even turn of sound on youtube. :slight_smile:

Music from this old funny anime about boxing, kind of allegro … easy fast move.
https://www.youtube.com/watch?v=5EuPGvhRxAI

Ruslan, for the developers, the paradigma website is a big weak point. You probably lose a lot of sales.

In your place, I’ll create a separate website dedicated to Xojo developers. It must be simple and clear. All the text would be focused on a single target: Xojo developer.

-A page on the presentation of the product (and in the Xojo context)
-A page on the strengths of the product (and in the Xojo context)
-A page on the price
-A page on the complementary products (studio, reports, priority support)
-A page on “how to start with Xojo and Valentina DB” (with for example a link to an installer that installs automatically all components, a link to a Xojo demo project, some tutorials or videos).
-The PDF manual

For prices:
Valentina DB Server for Xojo: $ 600
With Xojo classes, unlimited deployment, no royalties.
Thats all.

Technically, 5 simultaneous connections to a database as fast as Valentina, it actually fits dozens of simultaneous users. It is largely sufficient for 95% of users of Xojo. Then, if you have customers who have reached the limits of the database, you can suggest a ‘Valentina for medium and large companies’ version.

If you prefer to concentrate on development, why not work with a distributor who would do it? Someone like Philip would be perfect.

Thank you Oliver. I will show this to Lynn Fredricks. He cares about site.

Good presentation - yes, a dream.

Not so far we have try to make InfoGraphic of Valentina Product Line.
We hope this A4 PDF should help people to see the whole picture.
We have not plug it into site.

You can take a look on this PDF

i totally agree about the web site not being at all easy to use.

I have a feeling that valentina server is maybe a good proposition for my customers, but i get totally lost in all the options. i have asked the support for answers and they responded, but i need to spend days on it.

Well, as Oliver above suggests, think that exists only ONE option for VServer OEM

  • Valentina DB Server for Xojo: $ 600

For 95% of Xojo developers this is enough.

[quote=249157:@Ruslan Zasukhin]
Well, as Oliver above suggests, think that exists only ONE option for VServer OEM

  • Valentina DB Server for Xojo: $ 600

For 95% of Xojo developers this is enough.[/quote]

Yes, I suspect that will be ok for most of my customers, I have a few that may need more, but they wouldnt mind too much the price anyway.

Is there any ‘Easy’ way of replicating data from MSSQL into the valentinaDB. for reporting purposes, that would be cool!

By the way, i was trying to create a query using your tool and it has an issue.

when you have two tables linked and try to filter on a field that is in both tables (with the same name) you get an error about MSSQL not knowing which field you mean. its not possible to add the table before it either it seems.