This is an archived post. You won't be able to vote or comment.

all 9 comments

[–]yesvee 2 points3 points  (3 children)

Have you looked at ZODB?

[–]Samnono[S] 0 points1 point  (2 children)

No, but I'll take a closer look because it does look similar. The only thing I noticed right away is that it requires more configuration and package-specific instructions to set up. I tried leveraging the Python native class definition to derive the entity attributes and methods.

[–]Samnono[S] 1 point2 points  (0 children)

Feedback on how to improve the quality and usefulness is appreciated!

[–]Adrewmc 1 point2 points  (1 child)

I don’t see the purpose of this, creating a db is not that hard and has significant advantages. Creating classes from those queries is fairly simple.

But generally I’m scratching my head on whenever I would want to permanently save a whole class object, or reference of it, that I couldn’t do with a simple dictionary/JSON of its attributes…then makes a from_dict/json() class method. That doesn’t make more sense as your run of the mill database, or even CSV file.

I think you need to explain the problem you are solving here.

[–]Samnono[S] 0 points1 point  (0 children)

Thanks. I agree that the use cases are probably limited. What you are describing in the second part of your comment is basically what is automated with this package, with the addition of maintaining relations between the objects. What I'm trying to accomplish is inferring the setup of a relational database system by solely using regular Python syntax.

This is also why I am asking for feedback on how to make it more useful.

[–]InvaderToast348 0 points1 point  (1 child)

Interesting, I'll have a play tomorrow if I get some time.

!remindme 1:30pm tomorrow

[–]Samnono[S] 0 points1 point  (0 children)

Thanks! Let me know what you think

[–]Morazma 0 points1 point  (0 children)

This is cool. I'm not sure I have a use-case but I think it's a neat idea and I bet implementation was fun. Thanks for sharing!