memphis-iis / gludb Goto Github PK

New functionality - we should be able to change a table's name, recreate the table, and then do a full read/write.

Notes:

• We'll need a different algorithm for Dynamo
• We probably won't support GCD at first

Hello World!

In DBObject, we take control of init and give the user the setup method.

That's because Python method dispatch is MRO, named-based, and handled at runtime. That's all great, but if the original init that we replace manually called the superclass init, then our replacement init gets called. And that happens regardless of whether or not you use the super keyword. Another issue is the possibility of infinite recursion if you're not careful.

In fact, constructor call order with an arbitrary inheritance hierarchy is pretty difficult to support when your providing the kind of extra functionality we're talking about. That's why the design is switched - our special constructor is called once for the entire hierarchy and uses Python's MRO on class variables to determine what Fields it needs.

However, clobbering a user-supplied init is pretty much always a bad idea, so we should throw an exception. Something like:

prev_init = getattr(cls, "__init__", None)
if callable(prev_init) and prev_init != object.__init__:
    raise TypeError('Classes with user-supplied __init__ should not be decorated with DBObject. Use the setup method')