You may set LogToSysLog variable to 1 (in the INI file or via vServer properties) to make vServer put log messages into the system log:
* Event log for Windows
* SysLog for Linux.
The default state of variable is off.
Posts in English
You may set LogToSysLog variable to 1 (in the INI file or via vServer properties) to make vServer put log messages into the system log:
* Event log for Windows
* SysLog for Linux.
The default state of variable is off.
Working with Trevore Devore we have found that V4REV do not understand Binary Values if pass them into array of binds.
Problem is that external get array of MCstrings which contain {char*, len}. So external cannot differ strings from binaries.
Solution is like in REV DB. Developer must use prefix “*b” for array items, which contain binary values.
put 1 into binds[1]
put str into binds[2]
put binaryValue into binds[“*b3”]
VREV external now is able to analyze names of array and found binary values.
In some cases we can avoid copying sub-query result to the temporary table. We can even use sub-query cursor “as is” – so it could be used as a result of the whole query. In other words there is almost zero overhead against a simple query.
For now such optimization can be applied if a query:
Examples:
SELECT * FROM (SELECT * FROM t1 WHERE f1 > 5);
SELECT * FROM (SELECT t1.f1, t2 f1 FROM t1 JOIN t2 ON l1 WHERE t1.f1 > 5 AND t2.f1 <3);
We have add for VIEWs ability to be temporary, like we allow for Tables, Fields, Links. Temporary objects are not stored in the schema (.vdb file).
Also we have add for consistency IF NOT EXISTS clause to CREATE VIEW command.
New Video lessons added:
1) VStudio -> Import via ODBC datasource.
2) VStudio Pro -> Reports -> Grouping
3) VStudio Pro -> Reports -> Controls -> Picture Field
4) VStudio Pro -> Reports -> Regions -> Report Header
Now scripts show dialog to ask for ADMIN password, and execute load/unload of a VSERVER under SUDO.
We have add into v4.3 support of default parameters for stored procedures.
CREATE PROCEDURE( IN param INT = 2 ) …
Most Valentina SQL commands of kind CREATE SOMETHING have clause ‘OR REPLACE’. You should understand that this clause forces DROP of existed object before new will be created. This means that all its sub-objects also will be deleted. To avoid this use ALTER command.
For 4.3 we have add ALTER VIEW command.
Thorsten have found that on Snow Leopard VServer crashes if scheduler is enabled.
Problem was in ICU ucal_open() method. It looks that something was changed in the ICU used by 10.6. Now they require 3d parameter LocalName.
FIXED.
We have add 2 news video tutorials EN. One for MAC and one for WIN about how to setup ODBC datasource around Valentina ODBC driver.
http://valentina-db.com/dokuwiki/doku.php?id=valentina:video:video
These lessons can be helpful to setup ODBC data source for other dbs also, e.g. MySQL or MS Access, if you want import from then into Valentina using
Valentina Studio ODBC data import.
And lesson about this import from ODBC is our next lesson, which is in the work.
http://valentina-db.com/dokuwiki/doku.php?id=valentina:video:vspro:vspro
Here you can find new and improved video tutorials:
* Preview Overview
* SubReports
* Formatting
* Expression Field
New lessons now come in two languages English and Russian.
With 4.2 release we make Valentina for iPhone (iV4CC), which currently is VClient only, totally free for download and use. Of course you should have a license of a Valentina Server.
Note, that now you can easy download iV4CC and VServer Office archive with DEMO license, develop and test application on both Simulator and iPhone Device.
You can use this control to force page break for a report.
These buttons allow you easy import local project to a remote Valentina Server, and visa versa – remote project to local HDD.
Idea is simple: you choose local project, then vstudio create on a selected VSERVER a new project, and execute INSERTs record by record from your local project’s table. As result, you get on the VSERVER a new project with all the same items, which already registered and ready for use.
This is a very important feature for reports. And we have implement it using the same internal engine as the Valentina SQL format() function.
You can read Valentina WIKI: http://valentina-db.com/dokuwiki/doku.php?id=valentina:vcomponents:vsql:reference:expr:funcs_string#format
For any output field you can specify in the inspector its pattern and kind of pattern (number, currency, …).