i experimented a bit in the meantime and found out that the problem
here is my "index:unique" inside the keywords_i18n-schema. if i remove
the unique index from the schema declaration, i can edit existing
keyword entries in the backend without the mentioned validation error.
this is a workaround at the moment but no real solution, especially
because i have seen already schema declarations, for example the
jobeet one, where unique indexes and the backend interface work
together without problems. although i already examined the jobeet code
and compared it with my one, i couldn't really find the part of code
that makes the difference.
so, could someone point me to the right direction?
thanks, lowhsoe
> i'm currently having problems when i try to edit the values of an
> localized schema in the symfony backend.
> i use the following schema::
>
> keywords:
> _attributes: { phpName: Keywords, isI18N: true,
> i18nTable: keywords_i18n }
> id: ~
>
> keywords_i18n:
> _attributes: { phpName: KeywordsI18n }
> id: { type: integer, required: true, primaryKey: true,
> foreignTable: keywords, foreignReference: id }
> culture: { isCulture: true, type: varchar, size: 7, required:
> true, primaryKey: true }
> keyword: { type: varchar(255), required: true, index: unique }
>
> now, when i try to edit an exisiting keyword-entry, the validation
> engine throws the error "An object with the same "keyword" already
> exist." as i have a localized schema for 5 languages, this error
> message is displayed 5 times, e.g. one error message for every
> language-specific input field.
> what's my fault?
>
> regards,lowshoe
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
-~----------~----~----~----~------~----~------~--~---
