no one who can help? lowshoe
> 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 > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
