Im now setting up Valentina with Xojo (Hello from the Xojo Community!)
Now the plugin is installed and the server is up and running, is there a Valentina tutorial I can follow ?
Hit me on the PM and we can give you some pointers if you would like. The API reference in the Wiki is probably the best place to start.
We swear by binary links. It's refreshing to leave the old Primary/Foreign key thing behind. Same with ObjPtr. We started with both, but found binary links to be faster, more efficient, and easier to use when implementing solutions.
Ruslan Zasukhin wrote:
Hi Stephen,
our central place of docs - is Valentina WIKI:
http://www.valentina-db.com/docs/dokuwiki/v6/doku.php
Here on left side you can see Products -> Valentina for Xojo
It have section Getting Started with
* some tutorials.
* Migration to Valentina DB
* Migration to Valentina Server
Exists video tutorial about how to install Xojo plugin, VServer, VStudio.
Also in WIKI you can find FAQ sections.
Also you can find Articles section:
http://www.valentina-db.com/docs/dokuwiki/v6/doku.php?id=valentina:articles:articles
where you can see few articles about new SQLite Server, REST, notifications.
BTW, please specify your area of interest?
Scott wrote:
Welcome!
Valentina is a robust powerful database and reporting solution. We use it exclusively and have some pretty big clients with big demands (The mouse here in Orlando is one of our largest clients).
The only stumbling block you may encounter is the documentation. It's a little hard to follow - but once you get the hang of VDB it is a tremendous product. The developers are very helpful.
We learned along the way - making some pretty terrible mistakes - and we are still learning the finite details of VDB.
You set up a Vserver from what I see - we use Xojo also and the API method for most of our VDB code. I find it fast, efficient, and easy to code. If the VServer is not located on the same local network - I would recommend the SQL method.
We swear by binary links. It's refreshing to leave the old Primary/Foreign key thing behind. Same with ObjPtr. We started with both, but found binary links to be faster, more efficient, and easier to use when implementing solutions.
A nice feature of VDB is stored procedures. You can off load quite a bit of your business logic to the VServer.
The Reports ADK on VServer is awesome. I personally think it competes with, if not kicks Crystal Reports in the shorts for product features & price. The documentation is pretty minimal for Reports, however, and we learned mostly by trial and error.
We love it. The examples in the Paradigma folder after installation are pretty helpful. The youtube channel can give you basic information, although most of it is pretty dated.
Hit me on the PM and we can give you some pointers if you would like. The API reference in the Wiki is probably the best place to start.
We are a Mac shop and can't say enough positive things about VDB. It won us over for features and price.
Scott
Thank you for these pointers too. I am quite familiar with SQL for my needs but I see also there is a lot to learn about Valentina.
I also have a need for spatial functions since routing and road distances are a key part of the application. I do not see this in Valentina of course, but it could be done using SQLite/Spatialite operating from the client workstation instead of a central server.
It is good to see Valentina recently include SQLite as an option for the backend, which may be an option for the spatial functions, but would need to be able to load spatialite extension.
SQLite - Great database but not suited to network operation on the scale I need.
Ruslan Zasukhin wrote:
[code type="markup"]Thank you for these pointers too. I am quite familiar with SQL for my needs but I see also there is a lot to learn about Valentina.
Can I comment this?
Valentina DB is hybrid and flexible (like a woman?) :-)
* Valentina DB is Object-Relational DBMS.
This mean that all you know about Relationa model and SQL is correct here.
You must be able do all similar to other major SQL dbms, and it should work for you.
* Valentina DB can be used also as non-SQL.
* Key - Value? okay
* API way only? okay.
* ORM ... around SQL dbms, people often develop some ORM level, which hides SQL.
You work with some classes via API, later it is anyway is expanded into some SQL which go to DB.
Valentina even here has some extensions. e.g. You can work with extended methods of VCursor, and do VCursor.AddRecord() or VCursor.UpdateRecord() and magic is that SQL is NOT generated on client-side. To Server is sent small binary packet.
But let me underline, all this @sugar@, can be learned and played eventually, step by step.
And we still are on the track to a "more perfect state" :-)
Ruslan Zasukhin wrote:
I also have a need for spatial functions since routing and road distances are a key part of the application. I do not see this in Valentina of course, but it could be done using SQLite/Spatialite operating from the client workstation instead of a central server.
Well, you can show us what exactly you talk about in SQLite ...
I have see some extension for SQLite, comparing to postgreSQL support of "partial things" it is much simpler.
We can EASY add any FUNCTION on our C++ side, we have hundreds of them.
http://valentina-db.com/docs/dokuwiki/v6/doku.php?id=valentina:vcomponents:vsql:reference:expr:expr
Such function can be used in any SQL expression, and affect indexing, because we have indexing by expressions.
It is good to see Valentina recently include SQLite as an option for the backend, which may be an option for the spatial functions, but would need to be able to load spatialite extension.
Our developers told me that YES you must be able load SQLite extensions into our VSERVER, because this is possible todo via SQLite SQL.
Ruslan Zasukhin wrote:
SQLite - Great database but not suited to network operation on the scale I need.
Well, with Valentina SQLite Server - may be this changes.