Hi, I was testing out an application I am building when I came across a rather odd behaviour with a table that has a CamelCase class name and has a searchable behaviour.
Basically, when the index table is created Doctrine added a _ between the camel case. So the index table became camel_case_index rather than camelcase_index. When doing a delete operation on a record Doctrine UnitOfWork specifies the tablename as camelcase_index (and not camel_case_index). This creates a table not found error. The yml file does specify a table name but it seems that in circumstances this is ignored and the class name is used. I'm not sure whether the UnitOfWork is correct or whether the searchable behaviour is correct. I do find it somewhat bizare that niether searchable behaviour or the unitofwork seem to be paying attention to the table name. I tried changing the tablename in the yml file to produce a table that puts a _ between the camel case words, except UnitOfWork ignores the underscore.. I tried clearing the cache (Doctrine is being used as part of Symfony) and still no luck. Does anyone have any ideas or explanation as to why this behaviour might be happening? Does anyone have any ideas for a workaround other than renaming the table & class completely Regards, Simon -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com 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
