Is anyone using the

UniqueValidator

with the

cbValidation

module? It bombs out on line 61:

var IdValue  = invoke( target, "get#validationData.keyProperty#" );

with this error:

component [models.myModel] has no function with name [getid]

Indeed, my model does not have an

id

property nor a getter for it. Is this a requirement?

The unique validator uses the Id property to check if the current entity is refering to itself.

@Ryan Albrecht thank you for your response. So, this sql is all I would need:

var sql     = "Select 1 from #validationData.table# where #validationData.column# = :name";

No that would not work, because if you are UPDATING an entity that sql would return a record which would therefore fail the uniqueness check and you would not be able to update your entity. You are only thinking in terms of inserting into the database

It is not

id

, but ok... so as to my original question: it appears that an "id" property is a requirement? and/or a diff primary key needs to be passed in. That works now, thank you.

If your primary key is NOT

id

then just define it as Ryan is saying with those properties.

yep, I get that now... it's just not mentioned in any documentation that I found. So, it was a dive into the source to see why it's bombing.

Ok to answer your question. The

id

property is not specifically required but a property that defines your primary key is. By default the unique validator will assume it is called

id

. If it is different you can specify this in the validation declaration eg.

this.constraints = {
		team_name: { 
			unique = { 
				table : "team", 
				column : "name",
                //the unique validator will call getTeamId() on your object
				keyProperty: 'teamId', 
                //the unique validator will add the sql - 'and teamId <> :id'
				keyColumn: 'teamId'
			 }
		},
	};

Yea some docs suck or bare minimal given.

@Ryan Albrecht yes, thank you. I get it now... and pretty spot on that my field name is actually

team_name

and the PK is

teamID

... 👀

OOooohh snap you owe me a coke!

@Ryan Albrecht I don't suppose you've ever used a custom message in combination with the

unique

validator? I've tried adding a

uniqueMessage

in both the

team_name

parent struct and the

unique

struct, but it's not picked up in either? Other custom messages work fine.

I had this issue as well. Admittedly I did not spend a whole lot of time trying to solve it. I eventually just made a note to return to the issue one day and just moved on.

OK, thanks for the sanity check. It's not critical, just aesthetics.

looks like there is a bug in uniqueValidator class

Random but what occurs if you wrap your field name in

"team_name":

. I usually am just using cborm for this stuff not sure about the method for just cbvalidation tool.

Hi, 11 pm here 😀 . Not sure what your problem is now. But I know custom messages and metadata have their problems

Oops. Yeah if I comment that line out it works great. Also it seems this.name should be 'Unique' instead of 'uniqueValidator'

I think there is some serialization problem with meta data for some objects. And i18n messages also have their problems. I discovered even more problems but for fixing them cbvalidation needed some fundamental changes