Skip to content

fix: changing unique_constraints default #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
davewood wants to merge 1 commit into
base: master
Choose a base branch
from
Open

fix: changing unique_constraints default #8

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions lib/HTML/FormHandler/TraitFor/Model/DBIC.pm
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -178,13 +178,13 @@ For fields that are marked "unique", checks the database for uniqueness.
The unique constraints registered in the DBIC result source (see
L<DBIx::Class::ResultSource/add_unique_constraint>) will also be inspected
for uniqueness unless the field's 'unique' attribute is set to false.
Alternatively, you can use the C<unique_constraints>
attribute to limit uniqueness checking to only a select group of unique
Alternatively, you can override C<_build_unique_constraints>
to limit uniqueness checking to only a select group of unique
constraints. Error messages can be specified in the C<unique_messages>
attribute. Here's an example where you might want to specify a unique
widget name for a given department:

has '+unique_constraints' => ( default => sub { ['department_widget_name'] } );
override '_build_unique_constraints' => sub { return ['department_widget_name']; };
has '+unique_messages' => (
default => sub {
{ department_widget_name => "Please choose a unique widget name for this department" };
Expand Down