Some Questions: Json_Styles / 'Sys.Column' / Dbs Compatibility

[Dan Guerero]

Some Questions about VSTAR Release Candidate:

 

What happened with STYLE_JSON?

In Beta Versions of VSTAR, there was 2 Styles called 'JSON1' & 'JSON2', but now all json results are displayed using 'JSON2' Style, the statement throws error:

 

   SET STYLE_JSON TO 'JSON1'
|value error: STYLE_JSON
|   SET     STYLE_JSON TO'JSON1'
|[-0]

 

What happened with 'Sys.Column' Table?

Why is not 'Sys.Column' any more in Vstar?

 

 

Are the BETA Dbs compatibles whit Release Candidate Version?

Can i use in RC a Dbs created in Beta Version(2.1.17)?

 

vecto...@googlegroups.com

[Ernesto Herrera-Legorreta]

On Fri, Jun 12, 2009 at 5:32 PM, Dan Guerero <dan.gu...@dipros.com.mx> wrote:

Some Questions about VSTAR Release Candidate:

 

What happened with STYLE_JSON?

In Beta Versions of VSTAR, there was 2 Styles called 'JSON1' & 'JSON2', 

The different "styles" differed only in the levels of metadata provided along with the data. One provided none, the other provided some basic metadata (column names, types, etc.).

All these are now handled orthogonally (relative to the FORMAT option) with the METADATA option. So, in order to achieve the same result as before, set both the FORMAT and the METADATA options:

SET FORMAT TO 'JSON'

SET METADATA TO 'BASIC'

What happened with 'Sys.Column' Table?

Why is not 'Sys.Column' any more in Vstar?

Sys.Column is not a persistent table: it is "calculated", i.e., constructed on the fly, from the information on the disk. You found an important bug. We are already looking into it. Expect a fix on Monday or Tuesday.

Thanks for finding a reporting this error.

 

 

Are the BETA Dbs compatibles whit Release Candidate Version?

Can i use in RC a Dbs created in Beta Version(2.1.17)?

The binary format for the data hasn't changed in a long time (i.e., what's stored in the DAT files.

What *has* changed is some of the names of the metadirectories (indexes, sys, etc.) so you would have to manually adjust them to match the new ones. 

But the key point is that the *data* files themselves are totally compatible.

[danakil]

> the METADATA option. So, in order to achieve the same result as before, set
> both the FORMAT and the METADATA options:
>
> SET FORMAT TO 'JSON'
> SET METADATA TO 'BASIC'
>

Pardon me, my mistake: the METADATA options currently available for
the 'JSON' FORMAT are 'NONE' and 'EXTENDED', so you should try either:

SET METADATA TO 'NONE'

or

SET METADATA TO 'EXTENDED'

to obtain the behavior of the JSON1 and JSON2 styles, respectively.

[danakil]

It's late afternoon on Friday and we've had a long week... perhaps
this is why I keep fumbling my answer to your question.

If you tried my last example you probably got a "value error" message
for METADATA. Sorry, in my machine I have METADATA as an alias for
FORMAT_METADATA:

METADATA =: FORMAT_METADATA

(this will define the name METADATA in the "base" locale. it will be
gone when you exit your session unless you include it in your "ini"
file)

that's why I can do

SET METADATA TO ...whatever

rather than the full

SET FORMAT_METADATA TO ...

you either need to define the same alias, or else use the full option
name (FORMAT_METADATA).