Kirill has updated support for ShockWave for V4MD 4.2 on Windows.
With V4MD 4.2 release you again will be develop shockwave application, that are able connect to a remote Valentina Server from your SW applications.
Valentina SQL get powerful FORMAT() function.
Ivan have add into Valentina engine new very powerful FORMAT() function for SQL.
It provides great ability to convert numbers and date/times into string format.
Please read detailed syntax in the Valentina WIKI:
http://valentina-db.com/dokuwiki/doku.php?id=valentina:vcomponents:vsql:reference:expr:funcs_string#format
The same algorithms will be added in nearest time to Valentina Reports.
Valentina WIKI now supports FreeMind maps.
So we can develop FreeMind maps and use them in the WIKI docs.
V4REV get two new video-lessons.
1) how to install V4REV
2) how to prepare V4REV MAC app for deployment to a clean user computer.
VPHP MAC now works with MAMP.
We have improve VPHP 4.2 to enable use it with easy-to-use bundle MAMP.
Please read details about installation in the WIKI/VPHP/Manual section
VPHP 4.2 Supports PHP Data Objects
We added support of PDO into Valentina PHP – mac and linux are already done. A new vphp_pdo_ driver is included in the VPHP archive.
What the heck is PDO? Read on.
Keeping Up to Date on Valentina
Customers who have worked with Valentina know that it pays to keep up to date on releases. The development team is hard at work on Valentina release 4.2. There are few ways to keep up on new releases. Continue reading Keeping Up to Date on Valentina
Valentina for Director – Polished the Log files
Kirill says:
Was found that V4MD produces not very accurate V4MD.LOG file. So was made polishing of this issue to make sure that all functions print all parameters and return value nicely. The same was made for all properties of Xtras.
Improvements for stored procedures and binded queries
It was a huge improvement to solve the problem with a “second run” in stored procedures and binded queries. Sometimes there was an incorrect behavior because of “over-prepared” nodes. There was a workaround with “EXECUTE” statement (which is actually developed to prepare any SQL statement and execute one from another SQL statement). So now this workaround could be omitted.
Valentina for Ruby MAC Improved
We have improved Valentina for Ruby v4 on MAC.
Now we have single UB module vruby_fat_release.dylib instead of two _ppc_ and _i586_. This still perfectly works with Ruby.
The WIKI pages about MAC INSTALL are corrected and updated.
We corrected the Valentina.rb adapter to reflect changes in the SHOW commands in v4, which now produce cursor with columns that have prefix ‘fld_’
Valentina WIKI now have section “Video Tutorials”
Here we will grow set of vide tutorials
Report Control Picture now have property to specify picture by URL/path.
As result you can show in a report not only picture from DB, but from disk or by any URL.
MakeNewReport(index, db, query = NULL, …); Query now can be NULL on default.
MakeNewReport(
inIndex as integer,
inDatabase as VDatabase,
inQuery as String = NULL,
inCursorLocation as EVCursorLocation = kClientSide,
inLockType as EVLockType = kReadOnly,
inCursorDirection as EVCursorDirection = kForwardOnly ) as VReport
Starting from 4.1 parameter inQuery can be NULL. In this case will be used original query around which was designed report, i.e. query stored inside of project.
This simplify development because there is no need to copy/paste query 2 times. In the same time you still can specify different query: e.g. with different WHERE statement.
“LIMIT N” now can be used in additional places.
Was found a problem that in a stored procedure the assignment statement do not accept SELECT with LIMIT. This problem is fixed now. So you can have
procname
BEGIN
var = SELECT f1 FROM T WHERE … LIMIT 1
END
Hierarchical (Recursive) Queries in Valentina SQL
There are three new kind of queries specially designed for recursive (hierarchical) tables.
Such kind of tables are widely used. It could be human relationships, threaded forums and anything which might be described as tree-like data.
There are few common SQL ways to operate with such structures but all of them are too far from perfect.
Valentina introduces special kind of query which looks much more clear, natural and readable.
Syntax:
vext_recursive_table -- v4.1
: {ANCESTORS | BROTHERS | DESCENDANTS} OF vext_root_objects
[{TO|ON} LEVEL UINT] USING link_name [WITH {ROOT | ROOTS}]
vext_root_objects
: UINT
| variable_name
| ( search_condition )
Examples:
ANCESTORS OF (RecID IN(4,5)) ON LEVEL 1 USING l1 BROTHERS OF 4 ON LEVEL 2 USING l1 SELECT * FROM (ANCESTORS OF (RecID IN(4,5)) ON LEVEL 1 USING l1) WHERE f1 = 'Branch2'
See also:
* WIKI: Valentina SQL Reference: Hierarchical (Recursive) Queries for description of exact syntax of these commands and examples.
* WIKI: Article Hierarchical (Recursive) Queries in Valentina SQL