Revolution has a property to get an UTF16-encoded content – unicodeText. So we can easily get it doing something like this one:

put unicodeText of field “ValueField” into uniText

Seems to be ready to pass this value to some vField, but Revolution externals (including V4REV) receive the data as a char pointers. For UTF16 encoding the very first symbol is zero – so it is treated as a terminated zero and finally V4REV receives empty string. Obviously we should pass the data encoded with some single-byte code-page to avoid it. In most cases it could be UTF8. So we do following -

• Set appropriate IOEncoding property for the database first (we promise pass  any strings to this db as UTF8 and vice versa – any string received from this database will be in UTF8):

get VDatabase_IOEncoding( mDBRef, “UTF-8″ )

• Prepare UTF16 value:

• Reading data back:

get VTable_FirstRecord(inTblRef)

put VTable_Field( inTblRef, 1 ) into fldRef

put uniEncode( VField_Value( fldRef ), “UTF8″) into fldValue

Also, you can omit UTF16-UTF8 transformation using some “natural” code-page. But you should note it could be  OS dependent.

//If MacOS Then

get VDatabase_IOEncoding( mDBRef, “Macintosh” )

// else

get VDatabase_IOEncoding( mDBRef, “Latin1″ )

…

put text of field “ValueField” into myValue

// Reading data back:

get VTable_FirstRecord(inTblRef)

put VTable_Field( inTblRef, 1 ) into fldRef

put  VField_Value( fldRef ) into fldValue

Examples:
SET PROPERTY LogFilesLocation TO ‘myLogsFolder’;
GET PROPERTY LogFilesLocation;

or

SET PROPERTY LogFilesLocation OF SERVER TO ‘myLogsFolder’;
GET PROPERTY LogFilesLocation OF SERVER;

If kernel works under the vserver global LogFilesLocation is unavailable and you should operate with vserver’s LogFilesLocation property instead.

So I have start process of changes all our kernel and vserver XCODE projects and scripts to use for 64 bit targets separate folder  /usr/local/lib/vcomponents_x64.

VSERVER project will be corrected to use it and install it inside of self.

ADK 64 bits (and this is going to be in the nearest time VPHP_Standalone_x64, VSDK_x64, V4CC_X64) also will use this folder in installers.

Note that on Windows we already have two such folders:
/Program Files/Paradigma Software/vcomponents_win_vc
/Program Files (x86)/Paradigma Software/vcomponents_win_vc

On Linux we also do not have such problem, because linux-32 and linux-64 are separated itself.

Renewal means you get an additional 12 months of updates. To qualify for upgrade pricing, you must renew your Valentina licenses no later than the last day of your previous license.

How do you know when your license expires? The easiest way is to look at email you received that contained your serial number or license file. If you are unsure, you can also contact Valentina support through the online support system.

Paradigma will honor renewal pricing for all expired licenses through the end of June 2010, so if you haven’t upgraded your ADK or Valentina Developer Network in over a year, now is the time to take advantage of renewal pricing and get the current version of your product, plus an additional 12 months of updates.

In particular, vStudio operates with remote connections via multiple threads  and it was a source of some glitches and unexpected errors especially with a long queries.  Now there are no more errors like “EOF reached…” or “Broken packet received…” which were result of incorrect thread synch.

There are two ways to keep existed values altering ObjectPtr:

1. There is a global property – OnChangeTypeZeroPtr. It is set to true by default. But you may change it with following statement – “SET PROPERTY OnChangeTypeZeroPtr TO false”. After this altering ObjectPtr will prevent zeroing data (sure it will be nulls for records which are absent in the new target table).  This property is not “schema-storable” – so you should set it up on each run if you need it.
2. The first approach is a global setting – so you will be able to keep some ObjectPtr values even changing “target” table. So we implement one more way – much more simple because the only thing you should keep in your mind is – the values will be preserved until you touch “target table” ObjectPtr property (because all values will be valid for the same target anyway).

About Portland Code Camp

Portland Code Camp and SQL Saturday are combining and coordinating efforts to bring 700–800 regional software development professionals together for the opportunity to immerse themselves in seminars, presentations, group exploration, and networking. Participants will be able to engage in their preferred technology, as well as to sample other options, with a focus on extending information exchange and enhancing the cross pollination of ideas.

Portland Code Camp happens on May 22, 2010 at the University of Portland.

Problem was that VField.value in ObjC implemented as pair of methods (in other Valentina ADKs, e.g. Valentina for REALbasic it is a true property of class). So if to override this pair in the sub-classes then always will be called overridden methods.

To resolve issue, we have decide to rename these methods in all VField sub-classes. Rules now are simple:

a) for VField we have methods, which return and accept value is (id) object. If you have come to ObjC from other languages, you can think about (id) object as kind of VARIANT.

– (id) value;
- setValue: (id) inValue;

b) for all sub-classes of VField we name these pair of methods according to sub-class name. For example:

– (long) longValue;
- setLongValue: (long) inValue;

    - (float) floatValue;
    - setFloatValue: (float) inValue;

Bart have asked this function to be able produce UNIQUE INDEX for strings/texts bigger of 128 chars. This limit comes from fact that indexes of Valentina use pascal-like storage format for strings, e.g. 256 bytes maximum, 128 for UTF16.

And this new optimization is even better! It is also made on INDEX-level and affects absolutely ANY index search operation!! Especially we will see effect for searches that return many records into Set.

I see yet two possible steps to optimize speed of open for database.
* [minor] – …
* [major] – start to cache data in the algorithms that read schema from recursive sysItem table.

Target is to make time few seconds only.