cubicweb #809460 checking of schema.py for name conventions in attributes [open]
There are some valid schemas (from a yams point of view) which cannot be used in CW because of RQL restrictions, mainly in the naming of entities and their attributes. my current issue is an attribute with a name starting with an underscore: db-create works fine, RQL fails with syntax error. The checking performed on entity names (in cubicweb.schema.CubicwebSchema.add_entity_type should be generalized to other names which have limitations. | |
| priority | normal |
|---|---|
| type | enhancement |
| done in | <not specified> |
| closed by | <not specified> |
similar entities
- cubicweb #2110238 cache results of schema manipulation methods
- cubicweb #969169 [inline forms] do not show the 'remove' link if cardinality is '1x'
- cubicweb #246942 supporting aggregates in SET queries
- cubicweb #1947456 ORM should not try to re-fetch initiator relation/entity
- cubicweb #1381497 support substitution of list of elements passed to RQL IN predicate
[see all]
Comments
-
2010/03/29 13:51
add commentsyt says this might actually be an issue with the RQL grammar. IOW, RQL should accept such an attribute without complaining.