We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Hi,
When I try to save a category with the same name , because the slug has to be unique I get an Illuminate \ Database \ QueryException .
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'aaa' for key 'categories_slug_unique' (SQL: insert into categories (name, slug, description, order, updated_at, created_at) values (aaa, aaa, aaaa, 4, 2014-03-09 19:57:16, 2014-03-09 19:57:16))
categories
name
slug
description
order
updated_at
created_at
I will try to fix this in one fork soon, so if it will not be fixed meanwhile will propose a pull request, thx.
The text was updated successfully, but these errors were encountered:
Could you tell me the use case for having the same category twice? I can't think of a reason why you would want to have that :)
Sorry, something went wrong.
@stidges I think @cojocaru just means the exception should be caught
Oh of course... Sorry about that, thanks for the clarification :)
@dabernathy89, @stidges yep, this was what I meant, of course you never need the same name , esp for categories.
No branches or pull requests
Hi,
When I try to save a category with the same name , because the slug has to be unique I get an Illuminate \ Database \ QueryException .
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'aaa' for key 'categories_slug_unique' (SQL: insert into
categories
(name
,slug
,description
,order
,updated_at
,created_at
) values (aaa, aaa, aaaa, 4, 2014-03-09 19:57:16, 2014-03-09 19:57:16))I will try to fix this in one fork soon, so if it will not be fixed meanwhile will propose a pull request, thx.
The text was updated successfully, but these errors were encountered: