Hi,

Just upgraded to build 960 stable from 951, both client, server and bundles.

On a simple procedure of loading an existing document by id, updating 1
property (a DateTimeOffset property) I am getting an exception from the
UniqueConstraint bundle.

I can't seem to reproduce this locally on my dev machine but only on my
production server.

var account = _documentSession.Load<Account>(command.AccountId);

account.LastNotificationReadDate = DateTimeOffset.Now;

Raven.Database.Exceptions.OperationVetoedException: PUT vetoed by
Raven.Bundles.UniqueConstraints.UniqueConstraintsPutTrigger because: Ensure
unique constraint violated for fields: ArtistName, EMail

Has anything changed that could cause this, it was working fine before the
upgrade to latest stable.

Paul

I can reproduce this from the Silverlight management studio too, load up the
document, modify and save it.get the same error.

I have downgraded the server to build 951 just to check if it fixes it, but
it doesn't which is strange.

I'm not 100% sure it was build 951 I was using previously to be quite
honest, but it was around the 24th May i downloaded the latest build I was
using.

This is affecting a large proportion of my site currently when saving any
document related to a user account.

Paul

From: ravendb@googlegroups.com [mailto:ravendb@googlegroups.com] On Behalf
Of Paul Hinett
Sent: 08 June 2012 23:41
To: ravendb@googlegroups.com
Subject: [RavenDB] OperationVetoedException - when updating an existing
document

Hi,

Just upgraded to build 960 stable from 951, both client, server and bundles.

On a simple procedure of loading an existing document by id, updating 1
property (a DateTimeOffset property) I am getting an exception from the
UniqueConstraint bundle.

I can't seem to reproduce this locally on my dev machine but only on my
production server.

var account = _documentSession.Load<Account>(command.AccountId);

account.LastNotificationReadDate = DateTimeOffset.Now;

Raven.Database.Exceptions.OperationVetoedException: PUT vetoed by
Raven.Bundles.UniqueConstraints.UniqueConstraintsPutTrigger because: Ensure
unique constraint violated for fields: ArtistName, EMail

Has anything changed that could cause this, it was working fine before the
upgrade to latest stable.

Paul

Can you update to 960 ? 951 is unstable, and it has a bug related to unique
contraints.

On Sat, Jun 9, 2012 at 2:55 AM, Paul Hinett <p...@ukcreativedesigns.com>wrote:

I did this before, that is what caused the issue (I think).

I have updated to build 960 again and I'm running from the debug console,
still getting the same problem.

From: ravendb@googlegroups.com [mailto:ravendb@googlegroups.com] On Behalf
Of Paul Hinett
Sent: 09 June 2012 00:55
To: ravendb@googlegroups.com
Subject: RE: [RavenDB] OperationVetoedException - when updating an existing
document

I can reproduce this from the Silverlight management studio too, load up the
document, modify and save it.get the same error.

I have downgraded the server to build 951 just to check if it fixes it, but
it doesn't which is strange.

I'm not 100% sure it was build 951 I was using previously to be quite
honest, but it was around the 24th May i downloaded the latest build I was
using.

This is affecting a large proportion of my site currently when saving any
document related to a user account.

Paul

From: ravendb@googlegroups.com [mailto:ravendb@googlegroups.com] On Behalf
Of Paul Hinett
Sent: 08 June 2012 23:41
To: ravendb@googlegroups.com
Subject: [RavenDB] OperationVetoedException - when updating an existing
document

Hi,

Just upgraded to build 960 stable from 951, both client, server and bundles.

On a simple procedure of loading an existing document by id, updating 1
property (a DateTimeOffset property) I am getting an exception from the
UniqueConstraint bundle.

I can't seem to reproduce this locally on my dev machine but only on my
production server.

var account = _documentSession.Load<Account>(command.AccountId);

account.LastNotificationReadDate = DateTimeOffset.Now;

Raven.Database.Exceptions.OperationVetoedException: PUT vetoed by
Raven.Bundles.UniqueConstraints.UniqueConstraintsPutTrigger because: Ensure
unique constraint violated for fields: ArtistName, EMail

Has anything changed that could cause this, it was working fine before the
upgrade to latest stable.

Paul

Any way to repro?

It's not doing this locally on dev machine, only on production server with
any save to an existing 'Account' document.

I would do a backup/restore to my local machine to test, but it takes over
24 hours.

From: ravendb@googlegroups.com [mailto:ravendb@googlegroups.com] On Behalf
Of Oren Eini (Ayende Rahien)
Sent: 09 June 2012 11:27
To: ravendb@googlegroups.com
Subject: Re: [RavenDB] OperationVetoedException - when updating an existing
document

Any way to repro?

I did this before, that is what caused the issue (I think).

I have updated to build 960 again and I'm running from the debug console,
still getting the same problem.

From: ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');>
[mailto:ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');> ] On Behalf
Of Paul Hinett
Sent: 09 June 2012 00:55
To: ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');>
Subject: RE: [RavenDB] OperationVetoedException - when updating an existing
document

I can reproduce this from the Silverlight management studio too, load up the
document, modify and save it.get the same error.

I have downgraded the server to build 951 just to check if it fixes it, but
it doesn't which is strange.

I'm not 100% sure it was build 951 I was using previously to be quite
honest, but it was around the 24th May i downloaded the latest build I was
using.

This is affecting a large proportion of my site currently when saving any
document related to a user account.

Paul

From: ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');>
[mailto:ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');> ] On Behalf
Of Paul Hinett
Sent: 08 June 2012 23:41
To: ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');>
Subject: [RavenDB] OperationVetoedException - when updating an existing
document

Hi,

Just upgraded to build 960 stable from 951, both client, server and bundles.

On a simple procedure of loading an existing document by id, updating 1
property (a DateTimeOffset property) I am getting an exception from the
UniqueConstraint bundle.

I can't seem to reproduce this locally on my dev machine but only on my
production server.

var account = _documentSession.Load<Account>(command.AccountId);

account.LastNotificationReadDate = DateTimeOffset.Now;

Raven.Database.Exceptions.OperationVetoedException: PUT vetoed by
Raven.Bundles.UniqueConstraints.UniqueConstraintsPutTrigger because: Ensure
unique constraint violated for fields: ArtistName, EMail

Has anything changed that could cause this, it was working fine before the
upgrade to latest stable.

Paul

This is only happening on old documents by the way, newly created documents
seem to be working fine by the looks of it.

From: ravendb@googlegroups.com [mailto:ravendb@googlegroups.com] On Behalf
Of Oren Eini (Ayende Rahien)
Sent: 09 June 2012 11:27
To: ravendb@googlegroups.com
Subject: Re: [RavenDB] OperationVetoedException - when updating an existing
document

Any way to repro?

I did this before, that is what caused the issue (I think).

I have updated to build 960 again and I'm running from the debug console,
still getting the same problem.

From: ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');>
[mailto:ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');> ] On Behalf
Of Paul Hinett
Sent: 09 June 2012 00:55
To: ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');>
Subject: RE: [RavenDB] OperationVetoedException - when updating an existing
document

I can reproduce this from the Silverlight management studio too, load up the
document, modify and save it.get the same error.

I have downgraded the server to build 951 just to check if it fixes it, but
it doesn't which is strange.

I'm not 100% sure it was build 951 I was using previously to be quite
honest, but it was around the 24th May i downloaded the latest build I was
using.

This is affecting a large proportion of my site currently when saving any
document related to a user account.

Paul

From: ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');>
[mailto:ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');> ] On Behalf
Of Paul Hinett
Sent: 08 June 2012 23:41
To: ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');>
Subject: [RavenDB] OperationVetoedException - when updating an existing
document

Hi,

Just upgraded to build 960 stable from 951, both client, server and bundles.

On a simple procedure of loading an existing document by id, updating 1
property (a DateTimeOffset property) I am getting an exception from the
UniqueConstraint bundle.

I can't seem to reproduce this locally on my dev machine but only on my
production server.

var account = _documentSession.Load<Account>(command.AccountId);

account.LastNotificationReadDate = DateTimeOffset.Now;

Raven.Database.Exceptions.OperationVetoedException: PUT vetoed by
Raven.Bundles.UniqueConstraints.UniqueConstraintsPutTrigger because: Ensure
unique constraint violated for fields: ArtistName, EMail

Has anything changed that could cause this, it was working fine before the
upgrade to latest stable.

Paul

It seems to also only do this for specific documents, I'm not entirely sure
which ones exactly or if there is any pattern to this, but some save ok,
some don't.

From: ravendb@googlegroups.com [mailto:ravendb@googlegroups.com] On Behalf
Of Oren Eini (Ayende Rahien)
Sent: 09 June 2012 11:27
To: ravendb@googlegroups.com
Subject: Re: [RavenDB] OperationVetoedException - when updating an existing
document

Any way to repro?

I did this before, that is what caused the issue (I think).

I have updated to build 960 again and I'm running from the debug console,
still getting the same problem.

From: ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');>
[mailto:ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');> ] On Behalf
Of Paul Hinett
Sent: 09 June 2012 00:55
To: ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');>
Subject: RE: [RavenDB] OperationVetoedException - when updating an existing
document

I can reproduce this from the Silverlight management studio too, load up the
document, modify and save it.get the same error.

I have downgraded the server to build 951 just to check if it fixes it, but
it doesn't which is strange.

I'm not 100% sure it was build 951 I was using previously to be quite
honest, but it was around the 24th May i downloaded the latest build I was
using.

This is affecting a large proportion of my site currently when saving any
document related to a user account.

Paul

From: ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');>
[mailto:ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');> ] On Behalf
Of Paul Hinett
Sent: 08 June 2012 23:41
To: ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');>
Subject: [RavenDB] OperationVetoedException - when updating an existing
document

Hi,

Just upgraded to build 960 stable from 951, both client, server and bundles.

On a simple procedure of loading an existing document by id, updating 1
property (a DateTimeOffset property) I am getting an exception from the
UniqueConstraint bundle.

I can't seem to reproduce this locally on my dev machine but only on my
production server.

var account = _documentSession.Load<Account>(command.AccountId);

account.LastNotificationReadDate = DateTimeOffset.Now;

Raven.Database.Exceptions.OperationVetoedException: PUT vetoed by
Raven.Bundles.UniqueConstraints.UniqueConstraintsPutTrigger because: Ensure
unique constraint violated for fields: ArtistName, EMail

Has anything changed that could cause this, it was working fine before the
upgrade to latest stable.

Paul

I have noticed something weird.

In the actual unique constraint document of a working one, this is how it
looks:

{

  "RelatedId": "accounts-40132"

And a none working one:

{

  "Id": "accounts-155"

Why is one using RelatedId, and the other Id?

Is this maybe the issue?

Paul

From: ravendb@googlegroups.com [mailto:ravendb@googlegroups.com] On Behalf
Of Oren Eini (Ayende Rahien)
Sent: 09 June 2012 12:02
To: ravendb@googlegroups.com
Subject: Re: [RavenDB] OperationVetoedException - when updating an existing
document

Is it possible that you don't have the right metadata On those docs?

Can you get a failing doc, data + metadata ? Can you test on that?

It seems to also only do this for specific documents, I'm not entirely sure
which ones exactly or if there is any pattern to this, but some save ok,
some don't.

From: ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');>
[mailto:ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');> ] On Behalf
Of Oren Eini (Ayende Rahien)
Sent: 09 June 2012 11:27
To: ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');>
Subject: Re: [RavenDB] OperationVetoedException - when updating an existing
document

Any way to repro?

I did this before, that is what caused the issue (I think).

I have updated to build 960 again and I'm running from the debug console,
still getting the same problem.

From: ravendb@googlegroups.com [mailto:ravendb@googlegroups.com] On Behalf
Of Paul Hinett
Sent: 09 June 2012 00:55
To: ravendb@googlegroups.com
Subject: RE: [RavenDB] OperationVetoedException - when updating an existing
document

I can reproduce this from the Silverlight management studio too, load up the
document, modify and save it.get the same error.

I have downgraded the server to build 951 just to check if it fixes it, but
it doesn't which is strange.

I'm not 100% sure it was build 951 I was using previously to be quite
honest, but it was around the 24th May i downloaded the latest build I was
using.

This is affecting a large proportion of my site currently when saving any
document related to a user account.

Paul

From: ravendb@googlegroups.com [mailto:ravendb@googlegroups.com] On Behalf
Of Paul Hinett
Sent: 08 June 2012 23:41
To: ravendb@googlegroups.com
Subject: [RavenDB] OperationVetoedException - when updating an existing
document

Hi,

Just upgraded to build 960 stable from 951, both client, server and bundles.

On a simple procedure of loading an existing document by id, updating 1
property (a DateTimeOffset property) I am getting an exception from the
UniqueConstraint bundle.

I can't seem to reproduce this locally on my dev machine but only on my
production server.

var account = _documentSession.Load<Account>(command.AccountId);

account.LastNotificationReadDate = DateTimeOffset.Now;

Raven.Database.Exceptions.OperationVetoedException: PUT vetoed by
Raven.Bundles.UniqueConstraints.UniqueConstraintsPutTrigger because: Ensure
unique constraint violated for fields: ArtistName, EMail

Has anything changed that could cause this, it was working fine before the
upgrade to latest stable.

Paul<

Yes, we had a breaking change there, where we changed Id -> RelatedId
You can fix this by changing this.

On Sun, Jun 10, 2012 at 12:45 AM, Paul Hinett <p...@ukcreativedesigns.com>wrote:

Seems like an unnecessary breaking change?

Is there a list of breaking changes anywhere that I can check through when
upgrading server builds?

What would be the recommended way to loop through all the invalid unique
constraint documents and updating the Id field to RelatedId?

Paul

From: ravendb@googlegroups.com [mailto:ravendb@googlegroups.com] On Behalf
Of Paul Hinett
Sent: 09 June 2012 22:45
To: ravendb@googlegroups.com
Subject: RE: [RavenDB] OperationVetoedException - when updating an existing
document

I have noticed something weird.

In the actual unique constraint document of a working one, this is how it
looks:

{

  "RelatedId": "accounts-40132"

And a none working one:

{

  "Id": "accounts-155"

Why is one using RelatedId, and the other Id?

Is this maybe the issue?

Paul

From: ravendb@googlegroups.com [mailto:ravendb@googlegroups.com] On Behalf
Of Oren Eini (Ayende Rahien)
Sent: 09 June 2012 12:02
To: ravendb@googlegroups.com
Subject: Re: [RavenDB] OperationVetoedException - when updating an existing
document

Is it possible that you don't have the right metadata On those docs?

Can you get a failing doc, data + metadata ? Can you test on that?

It seems to also only do this for specific documents, I'm not entirely sure
which ones exactly or if there is any pattern to this, but some save ok,
some don't.

From: ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');>
[mailto:ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');> ] On Behalf
Of Oren Eini (Ayende Rahien)
Sent: 09 June 2012 11:27
To: ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');>
Subject: Re: [RavenDB] OperationVetoedException - when updating an existing
document

Any way to repro?

I did this before, that is what caused the issue (I think).

I have updated to build 960 again and I'm running from the debug console,
still getting the same problem.

From: ravendb@googlegroups.com [mailto:ravendb@googlegroups.com] On Behalf
Of Paul Hinett
Sent: 09 June 2012 00:55
To: ravendb@googlegroups.com
Subject: RE: [RavenDB] OperationVetoedException - when updating an existing
document

I can reproduce this from the Silverlight management studio too, load up the
document, modify and save it.get the same error.

I have downgraded the server to build 951 just to check if it fixes it, but
it doesn't which is strange.

I'm not 100% sure it was build 951 I was using previously to be quite
honest, but it was around the 24th May i downloaded the latest build I was
using.

This is affecting a large proportion of my site currently when saving any
document related to a user account.

Paul

From: ravendb@googlegroups.com [mailto:ravendb@googlegroups.com] On Behalf
Of Paul Hinett
Sent: 08 June 2012 23:41
To: ravendb@googlegroups.com
Subject: [RavenDB] OperationVetoedException - when updating an existing
document

Hi,

Just upgraded to build 960 stable from 951, both client, server and bundles.

On a simple procedure of loading an existing document by id, updating 1
property (a DateTimeOffset property) I am getting an exception from the
UniqueConstraint bundle.

I can't seem to reproduce this locally on my dev machine but only on my
production server.

var account = _documentSession.Load<Account>(command.AccountId);

account.LastNotificationReadDate = DateTimeOffset.Now;

Raven.Database.Exceptions.OperationVetoedException: PUT vetoed by
Raven.Bundles.UniqueConstraints.UniqueConstraintsPutTrigger because: Ensure
unique constraint violated for fields: ArtistName, EMail

Has anything changed that could cause this, it was working fine before the
upgrade to latest stable.

Paul<

http://issues.hibernatingrhinos.com/<http://issues.hibernatingrhinos.com/dashboard>
can
give the breaking changes.

It was needed because Id is the default identifier property.

For updating, you can use:
http://ravendb.net/docs/http-api/http-api-multi
http://ravendb.net/docs/client-api/partial-document-updates

On Sun, Jun 10, 2012 at 1:07 PM, Paul Hinett <p...@ukcreativedesigns.com>wrote: