… although Vstudio linux is installed into /opt location, it loads /usr/local/lib/vcomponents if they present.
Today this issue was solved. Into script that start Vstudio, was added pre-load for vcomponents dlls. After this one dll have start cause problem because it contains static library that is newer than system’s one. Many hours was not successful, because of GCC 4.2 bug… Finally, a “brutal force trick” was used (the second time) to workaround this issue.
In a case of crash, Valentina Studio on linux and windows now is able to create text file that contains crash log information (stack of calls, loaded DLLs, … ). MAC OS X version of VStudio have no need to do this because OS X itself generates such crash log.
On the next start Valentina Studio will show dialog with suggestion to send this crash log to Valentina-db.com. Please note, this crash log contains totally anonymous information. This information will help to Valentina team to see that there was fact of crash, and where exactly was crash. You can set check box to not show this dialog future and just send a crash report automatically if it is found.
On Windows and Linux, after sending of crash log file, it is deleted from disk of your computer. On OS X it is not deleted, because OS X append them into single file per application.
Ladies and Gentlemen!
The first time in the world! 🙂
Localizable Enum Type in DBMS!
We already many months have working ENUM type in 5.0 branch of Valentina. Let me remind that ENUM type is not from SQL standard, so different DBs implement it in different way if at all implement. We have implemented it using CREATE TYPE command of SQL Standard. And we have implement ENUM in way similar to PostgreSQL, because it is the most correct: you just CREATE TYPE ENUM once and later using it in all places of your database.
mySQL, in contrast, defines ENUM as part of a particular Table, right in the CREATE TABLE command. This is not good of course, because then you cannot use this type in other tables or for variables of Stored Procedures.
CREATE TABLE sizes (
name ENUM('small', 'medium', 'large')
);
It is interesting that such mature database as Oracle do not have ENUM type.
All these existed implementations have one big problem from our point of view: such enum types contains string values of only one language. Below we will describe our solution.
During testing of Valentina Studio one user have point that Schemas of PostgreSQL are not supported in VStudio yet. So we have spend almost 2 weeks to implement support of schemas for PostgreSQL on all levels:
Now we have two separate wikis to keep docs of v4 and v5:
We have add into Valentina Studio feature “Check Updates”. Only Mac App Store version will not have it, because AppStore itself take care about updates.
On start Valentina Studio will send a GET query to valentina-db site. This will happens in separate thread to not delay user in the case of network trouble.
You will be able enable/disable this feature in prefs panel, also you can specify if report about beta builds of vstudio.
I want note, that in this GET query we also will send some anonymous information such as:
Subject explains all.
Will be available for the next 5.0b40 build.
We have made first step to support iCloud technology from Apple.
Now Valentina Studio for MAC OS X (and only one, which is download from MacAppStore) will have iCloud prefs pane, that allows you to specify what to synch in the iCloud. For now this is bookmarks and resent connections to db servers.
Continue reading [NEW] VStudio + iValentina now sync bookmarks using iCloud
This tool now can work with Valentina Server, PostgreSQL and mySQL.
This is the central place where you can:
We was able embed into Valentina Studio plugin the pg_dump engine to dump a database into different formats of text files and load these text files back into database.
You can access these dump/load commands from the File menu of Valentina Studio application or from the contextual menu of a database object.
Continue reading [NEW] Valentina Studio – Postgre plugin – now can dump/load using pg_dump engine
This feature can be turned on/off in the preferences of Valentina Studio application. By default it is ON, because this provides natural behavior of schema editor.
We have made last days many polish of keyboard shortcuts in the SQL Editor and in the Schema Editor.
Schema Editor – its shortcuts correspond to Apple Safari:
| Back | cmd + [ |
|---|---|
| Forward | cmd + ] |
| Previous TAB | cmd + shift + { |
| Next TAB | cmd + shift + } |
SQL Editor also adopts its shortcuts to use standards of corresponded OS.
Valentina Engine far ago produce warnings in the ‘Warning.log’ for Import of Text operation. For example, record is not added if the primary key is not unique.
This warning.log is created near to application. And if this is a remote Valentina Server then user of Valentina Studio cannot easy see that warnings. Now this is improved. In Valentina engine, in Valentina Server and in Valentina Studio. Snapshot below demonstrate this.
In 5.0b30 we have return back QueryBulder after few months.
* new – it works now for all supported engines: Valentina, PostgreSQL, mySQL, SQLite.
* new – we have simplify interface removing few visible areas, replacing them on TAB panels. Note that you can switch by main panels using such shortcuts as cmd+1 and cmd+2.
* new – you can specify expressions to be used in the SELECT clause.
* note that you can specify inner and left/right/full outer joins using right-click on a link on the diagram.
* note that if you will click SQL panel and then continue develop diagramm then you will see live changes in the generated SQL.
We have added a new SQL command that works with VServer only to show tail of VServer.log file. (5.0b30)
TODO Valentina Studio now have a special panel where user can easy see this log using new command.
All together this simplify a lots work with remote VServer, especially if you do not have SSH access to its file system.