undefiened field in schema-full mode

[Yuri Makhno]

Hi,

Is it possible to restrict adding document that has field which is
undefined in the schema?

Hor example if schema has class: TestClass(a : String, b : String), I
shouldn't be able to add following document: { "@class" : "TestClass",
"a" : "a", "c" : "c", "b" : "b" } because it has "c" field, but
propery "c" is undefined in the schema.
If yes, how can I turn on such validation?

Regards,
Yuri

[Luca Garulli]

Hi,

this is really needed to get working as schema-full-strict mode.

I think it could be implemented like:

OClass.setStrict( boolean )

Setting to true a check is made, otherwise works like now.

Can you add a new issue for this?

Lvc@

[Anton Terekhov]

Luca, is it'll be possible to use strict mode via binary?

[Anton Terekhov]

There is an old issue about this http://code.google.com/p/orient/issues/detail?id=312

[Luca Garulli]

Hi,

course it will work.

By the way have you a better name for it?

OClass.setStrict( boolean ) - default FALSE

OClass.allowAdditionalFields( boolean ) - default TRUE

Lvc@

[Anton Terekhov]

Luca, these functions are per class on client or per class on server ( also saved in schema)?

[Yuri Makhno]

Hi,

Thanks for the answer!

I've created new feature request: http://code.google.com/p/orient/issues/detail?id=684

On 19 янв, 21:37, Luca Garulli <l.garu...@gmail.com> wrote:
> Hi,
> this is really needed to get working as schema-full-strict mode.
>
> I think it could be implemented like:
>
> OClass.setStrict( boolean )
>
> Setting to true a check is made, otherwise works like now.
>
> Can you add a new issue for this?
>
> Lvc@
>

[Luca Garulli]

Hi Anton,

what you mean?

Lvc@

[Anton Terekhov]

Luca, hi.

I just mean can two clients (first with OClass.setStrict(true) second with OClass.setStrict(false)) both communicate to same class on same DB?

[Luca Garulli]

The class is set at server side, so if a client change the setting with:

ALTER CLASS Employee STRICTMODE true

all the client updates/saves will be validated against the new settings.

Lvc@

[Luca Garulli]

Fixed issue 684 in SVN r4636.

Use OClass.setStrictMode(boolean)

or

ALTER CLASS Employee STRICTMODE true

Lvc@