-
Notifications
You must be signed in to change notification settings - Fork 25
Problem with Composite ... #7
Comments
There's two things going on here, a documentation bug and an API bug. Right now, Flywheel intentionally disables certain functionality for private fields (starting with '_'). The first problem is that this isn't documented, and it really should be. The second problem is that it's not intuitive and should behave better. That's just poor design on my part. I'm making a change at the moment which will fix your issue and then I'll update the docs accordingly. I should have this in today and I'll release 0.1.2 some time tomorrow. If you need the model working before then, you can temporarily remove the leading underscore from all the fields. Thanks for finding this issue! |
0.1.2 is released on pypi. Just to clear up all the edge cases, your current model should now work. Fields will not work if they begin with a double-underscore or end with a single underscore.
If you are using undeclared fields, any field that begins or ends with an underscore will not be persisted to Dynamo.
|
Thanks for the information. I looked at the dynamodb spec for column names and thought they were OK. Peace Sent from Yahoo Mail on Android |
Here is my schema...
When I set initialize everything and do a 'eng.save()' I get the following error returned:
boto.dynamodb.exceptions.DynamoDBNumberError: BotoClientError: TypeError numeric for
<flywheel.fields.Composite object at 0x9eece2c>
Cannot convert <flywheel.fields.Composite object at 0x9eece2c> to Decimal
This must be wrong.
The text was updated successfully, but these errors were encountered: