Ilya Priven

I agree. The goal of this option was to compensate for another bad design choice, which is that `default` applies to both "new' and "existing" models. Admittedly, "new" and "existing"...

@garrettheel, any thoughts on that? I would rather have an API where models aren't dealing with auth or host. For that we'd need a public API for setting it globally....

PynamoDB models are also effectively "tables", i.e. they deal with the details of how tables and their indices are defined. Perhaps instead of trying to create a new "table" class...

I'm afk now but the approach I'd probably take is to create two attributes: ``` NumberAttribute(null=True, attr_name="my_legacy_bool") BooleanAttribute(null=True, attr_name="my_legacy_bool") ``` 1. Make a change where your application checks them both...

This works similarly to how descriptors work in Python. ```python class C: @property def a(self): return 42 ``` or the equivalent form that's more similar to how PynamoDB uses attributes:...

The fact that `MyModel.x` and `MyModel().x` is not the same is intentional and expected behavior (the former references the attribute instance, the latter references the deserialized data). This is how...

It might be a good idea -- wasted plenty of time myself over this (naive when setting for the first time, UTC when reading -- and then arithmetics blow up).

Agree, we should fix this.

Generally the task of an ORM is to map raw data using a schema. If you don't need or care about a schema, perhaps using boto directly would in fact...

How many models does your application use and how large do you expect the boto client memory usage to be?