I'm surprised it wasn't licensed under the WTFPL (https://en.wikipedia.org/wiki/Do_What_The_Fuck_You_Want)
ButterDB
31–40 of 45 posts
Re: ButterDB
#32This is a potentially useful project but I could never use it for fear of "FuckItDB" appearing in an exception call trace that a client might see. Names don't have to mean anything, but certain names are still unacceptable.
According to this commit, the name was changed to butterdb about three months ago. https://github.com/Widdershin/butterdb/commit/6a73c9199d53f5... Digging on PyPI, I found the new package named butterdb. The version is bumped from .13 to .14, though that might just be the name change. In any case, it might be a good idea to change the submission to reflect the new name and the new package. https://pypi.python.org/pyp…
We changed the title and URL to the new name.
Re: ButterDB
#33Earlier quoted context omitted.
Although the WTFPL website ( http://www.wtfpl.net/faq/ ) does note somewhat ominously that it hasn't been tested in courts, it seems legitimate enough to me. Is there any evidence outside of its lack of history in court that would indicate it isn't suitable for production use? EDIT: gnu.org also says "We do not recommend this license" ,pointing to the Apache license as providing better protection against 'patent trea…
I think the main thing is that even if you literally don't care what the fuck happens with your code you should at least make a statement that absolves you of responsibility, such as "THIS SOFTWARE COMES WITH NO WARRANTY" etc.
I'm annoyed we live in a world where such a thing isn't clearly implied by the licence.
Re: ButterDB
#34ORM Stands for Object Relational Mapper. ORMS are software packages that map objects (class instances) to relational database tables (among other relational structures) and vice versa.
So maybe I'm nitpicking here but this project is not an ORM. There is no relational database here. Also it doesn't do joins, doesn't instrument attributes, makes no effort to convert object hierarchies to flat tables, etc, etc.
This is a (de)serialization library for google spreadsheets. Not much different from a CSV, XLS or even html table (de)serializer.
It's a nice hack though and certainly got its uses.
Re: ButterDB
#35Earlier quoted context omitted.
I think the main thing is that even if you literally don't care what the fuck happens with your code you should at least make a statement that absolves you of responsibility, such as "THIS SOFTWARE COMES WITH NO WARRANTY" etc.
I'm annoyed we live in a world where such a thing isn't clearly implied by the licence.
If by "the world" you mean "the US", then yes.
Re: ButterDB
#36ORM Stands for Object Relational Mapper. ORMS are software packages that map objects (class instances) to relational database tables (among other relational structures) and vice versa. So maybe I'm nitpicking here but this project is not an ORM. There is no relational database here. Also it doesn't do joins, doesn't instrument attributes, makes no effort to convert object hierarchies to flat tables, etc, etc. This is…
This is totally true. I simply hadn't thought of a better way to put it than ORM. I think it could be best put as an object spreadsheet mapper.
Re: ButterDB
#37ORM Stands for Object Relational Mapper. ORMS are software packages that map objects (class instances) to relational database tables (among other relational structures) and vice versa. So maybe I'm nitpicking here but this project is not an ORM. There is no relational database here. Also it doesn't do joins, doesn't instrument attributes, makes no effort to convert object hierarchies to flat tables, etc, etc. This is…
This is totally true. I simply hadn't thought of a better way to put it than ORM. I think it could be best put as an object spreadsheet mapper.
"Adapter"?
Re: ButterDB
#38ORM Stands for Object Relational Mapper. ORMS are software packages that map objects (class instances) to relational database tables (among other relational structures) and vice versa. So maybe I'm nitpicking here but this project is not an ORM. There is no relational database here. Also it doesn't do joins, doesn't instrument attributes, makes no effort to convert object hierarchies to flat tables, etc, etc. This is…
This is totally true. I simply hadn't thought of a better way to put it than ORM. I think it could be best put as an object spreadsheet mapper.
Maybe just 'Mapper'? As it is exactly what it does - maps spreadsheets to Python objects
Re: ButterDB
#39ORM Stands for Object Relational Mapper. ORMS are software packages that map objects (class instances) to relational database tables (among other relational structures) and vice versa. So maybe I'm nitpicking here but this project is not an ORM. There is no relational database here. Also it doesn't do joins, doesn't instrument attributes, makes no effort to convert object hierarchies to flat tables, etc, etc. This is…
This is totally true. I simply hadn't thought of a better way to put it than ORM. I think it could be best put as an object spreadsheet mapper.
ORM-like?
Re: ButterDB
#40ORM Stands for Object Relational Mapper. ORMS are software packages that map objects (class instances) to relational database tables (among other relational structures) and vice versa. So maybe I'm nitpicking here but this project is not an ORM. There is no relational database here. Also it doesn't do joins, doesn't instrument attributes, makes no effort to convert object hierarchies to flat tables, etc, etc. This is…
While technically true, you can somewhat simulate relational data. It would be interesting to see if any object-relational impedance mismatches are addressed.
Keep in mind languages evolve over time and definitions change ;)