You’ll be seeing real soon now the preview of SQLite support in Valentina Server.
[quote=171894:@Markus Winter]Valentina Server /5 ("slash 5) is free for non-profits, academic use and internal use / evaluation by you.
To deploy the free 5 connection version to customers you need VDN which is $599 per year ($360 renewal)[/quote]
This is about right, but the license is a bit more permissive in that the renewal is access to the latest versions. Lets say your 12 month period ends on version 6.6.6 (we will have to code name that one “Damien”) on December 31, 2015. 6.6.7 comes out on January 1, 2016. You’d still be able to deploy 6.6.6 thereafter.
I should point out too that there’s a 25% discount coupon for VDN for Omegabundle for Xojo 2014 purchasers, who order VDN before March 15, 2015. Also, a fresh bit of additional information on our blog that was posted today.
Good to know. I don’t think I read that anywhere, so maybe more info on your website would be good.
The base server will also have 10 SQLite connections, too (not just the 5 Valentina DB ones).
Hi Markus, actually this same as with Xojo price and renew. right?
One year of free updates means that you get updates for free during year.
After that you own and can use latest update as long as you want. Even 10 years.
Same rule for both Xojo and Valentina products.
Renew price just provide discount for active developers.
Hello guys,
official cubeSQL 5 announcement with more information about this release is available from:
http://www.sqlabs.com/blog/2015/03/announcing-cubesql-5/
For new and current users I’ll setup a very special time limited offer by the end of the week.
Thanks a lot for your continue support.
And install on a clean Yosemite setup (VMware) fails miserably as well:
Hi Oliver, when i install the new cubesql server, it ask if u want to include the startup script and i say yes. I just reboot my machine and check the system preference, and it show as running.
[quote=171996:@Oliver Osswald]And install on a clean Yosemite setup (VMware) fails miserably as well:
[/quote]
I’m seeing this on Mavericks too, both with and without the scripts.
You probably get the error ‘cp: /usr/local/bin/cubesql’ on a clean install because ‘cubeSQL Install.scpt’ does not create the directory /usr/local/bin (and it doesn’t exist on a clean install). so the ‘cp’ fails.
If you install it that way, you’ll need to tweak the script accordingly.
- check/create the directory ‘/usr/local/bin’ first
- set the owner and permission properly: (root:wheel)
We still do it the ‘old fashioned way’ with PackageMaker.
For Yosemite:
- add the /Library/LaunchDaemons/com.sqlabs.cubesql.plist
- PostInstall-Script for the LaunchDaemon-plist: chmod 644, chown root:wheel
- launch server: /bin/launchctl load -w /Library/LaunchDaemons/com.sqlabs.cubesql.plist
Possible workaround.
Installing here on OSX Mavericks.
Install the previous version 4.x.
Don’t reboot.
Install the new version 5 with scripts.
Register.
Reboot.
Edit : Check firewall settings. Incoming connections for cubesql were blocked by default ; changed this to allow and all appears ok so far.
As a Dev, I don’t like this model. I want free development because I SELL the DB licenses for the DB company, and I wish limited free connections (what about 2 or 3?) for ANYONE, and USERS paying for their extra licenses. So, when I develop a small system to be used by 5 people in a small business, a tester and a manager can play with the system before buying. Using a DB sales model with 3 free licenses and $50/per seat for each additional connection, the final user would buy a pack of 2 extra seat licenses ($100) to get those 5 connections.
Hello guys,
I am sorry for the problem on a fresh Yosemite install.
I fixed the issue and a new MacOS X installer is available from:
http://www.sqlabs.com/download/cubesql/500/cubeSQL.dmg
Hope this helps.
Automatic startup only started to work after I completely removed the previous installation. Update does not seem to work out of the box.
What remains for me, is the the “incoming connections” issue: Even if I allow incoming connections in the firewall settings of Mavericks, it is not actually doing that. I have no access to the server from another workstation until I disable the firewall completely.
@ Stephen and Jürg: I have no problem to do all these workarounds myself.
The problem is that until 4.5 one could recommend to any normal user to simply download and install that server on his workstation, in the same way they would install any other software on their machine. But if this is not working out of the box, then this becomes worthless. Then I recommend to go Postgresql. (Or maybe valentina in the future, we’ll see)
And that I have to spend this day with getting things to run again which used to be rocksolid, this is just %&*"$$$!!
Thanks Lynn, check my review on how about the current dev/licensing does not fit well for me (and probably hundreds of small devs).
The new installer does not fix the denial of incoming connections.
Even after allowing connections in the firewall for /usr/local/bin/cubesql it rejects any connection from the LAN.
The workaround is to disable the firewall, go figure …
Problaby they should play with pfctl command and /etc/pf.conf to include their firewall rules for macs
As the developer of your solution, you are the final gatekeeper of how your application works for your customers - that’s how we view the relationship. If your customer were forced to come to us to buy additional licenses, that would really limit what you can achieve in terms of your own business model*.
You could code your application so it only allows a single or a few connections at once. With our business model, you aren’t having to pay us, the DB company, anything additional for the first five connections.
Its actually pretty rare for us for developers to want US to sell to THEIR customers. We have a model for that too, where a customer can buy a copy of Valentina Server on their own. In that case, we provide support directly to them within the parameters of our license.
But the typical customer we have for VDN doesn’t want us involved with their customer. They’ve set up their own model, which can include support, or may include some modifications that pretty much conceal they are using our database (there’s a lot you can do with modifying db files, extensions, etc).
*If a VDN customer wants to sell a “full version” of Valentina Server, we give them a 20% reseller’s discount. We aren’t allergic to reseller sales at all.
Your business is your business, run it as you prefer. I have “tightwad” customers in a budgeted market, nobody wants “to buy a DB server software” but they would wish to buy “low cost expansion packs for enabling more clients”, probably adding seat licenses in the “pay-as-you-go” model. I do prefer they own those licenses, not me; and I do prefer they pay for such expansions and not me. Seems I am off the curve. 
For now I’ll keep it in the fatty and hard way, using PostgreSQL. 
Hello guys,
just a quick cubeSQL update.
I have just released version 5.0.1 with some fixes and improvements.
I also posted a new blog post where I describe how to address the Mavericks/Yosemite firewall issue.
There is also a very special, limited time offer for cubeSQL 5 available from:
http://www.sqlabs.com/cubesql_special_offer.php