-
Notifications
You must be signed in to change notification settings - Fork 59
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.
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
orm.em.options / mappings (type = annotations) / namespace cannot be empty #8
Comments
@quazardous Can you point to specific part of those docs that describe what you are saying? I'd be happy to look into this but most of the stuff I've looked at RE: annotations have still required a namespace. Also, if you can share your specific use case that would be helpful. I apologize for the delay on this. |
First example in ORM doctrine doc:
There is no namespace. I tried something like that to learn:
But i got an error. This is not very important in real case ;p |
OK. :) Mind if I close this issue then? |
man it's your code ;p do as you pleaz ;p |
Who doesn't use namespaces? :P |
try "namespace" => "\" |
I believe the feedback I got from one of the Doctrine team people (can't remember who answered me anymore) was that it had to do with the chain driver requiring a namespace. @dominikzogg Have you tested it with |
@simensen nah, it was only a suggestion |
In the ORM doc :
http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/tutorials/getting-started.html
You can have entity class without namespace.
but an error occurs if you let namespace option empty for annotations mapping.
The text was updated successfully, but these errors were encountered: