5 ms·

Hey folks, I'm the author of this library. I actually renamed it to 'butterdb' a while ago because some people found fuckitdb hard to swallow. You can check ou

Hey folks, I'm the author of this library. I actually renamed it to 'butterdb' a while ago because some people found fuckitdb hard to swallow. You can check out the code here: https://github.com/Widdershin/butterdb https://github.com/Widdershin/butterdb. I have grown a bit as a programmer since then, but I appreciate any feedback you might have. I actually used this in production against my own recommendation to run the matching for /r/longboarding's Secret Santa. All of our data came from Google Forms, so it just made sense. Hit me up if you have any questions.

ejr 12y ago
Thanks for writing this. Do you have plans to extend this to any locally stored spreadsheets? Ex: Excel, Calc (Libre and Open Office) and so on. I imagine even XML based documents would still present some vendor quirks to overcome.
- Widdershin 12y ago
  I have considered it, and just opened an issue to track demand (https://github.com/Widdershin/butterdb/issues/14 https://github.com/Widdershin/butterdb/issues/14). I would probably use another library to handle parsing (and hopefully avoid some of those pitfalls), just like I rely on gspread to handle all Google Spreadsheets integration. If you'd use butterdb if it had that feature, please let me know.
  - ejr 12y ago
    Thank you. I would use it right now actually as I do have some spreadsheets with Google. There are some I'd rather use locally like this and it would be just a nice extra. It would also avoid the need to maintain a network connection.
    - Widdershin 12y ago
      I'll definitely implement that at some point then. It's quite easy to swap out the database the model is backed by, so shouldn't be too hard.
  - clxl 12y ago
    I explored this a bit (based off of the javascript-based http://sheetjs.com/sexql/ http://sheetjs.com/sexql/) but the biggest difficulty is that people use CSVs and excel files in completely different ways for the same general task. In particular, different people set up budget workbooks in very different ways. There are also input problems and invalid files to deal with, so even if you manage to craft a meaningful integration you'd still have to figure out how to determine the structure and fix subtle non-uniformities
shangxiao 12y ago
lol, when I was younger I learned that you can't use names like "fuckitdb" in front of customers / business stakeholders. Some better known software packages have also changed their names: FCKeditor, Testacular

ejr 12y ago

Thanks for writing this. Do you have plans to extend this to any locally stored spreadsheets? Ex: Excel, Calc (Libre and Open Office) and so on. I imagine even XML based documents would still present some vendor quirks to overcome.

Widdershin 12y ago
I have considered it, and just opened an issue to track demand (https://github.com/Widdershin/butterdb/issues/14 https://github.com/Widdershin/butterdb/issues/14). I would probably use another library to handle parsing (and hopefully avoid some of those pitfalls), just like I rely on gspread to handle all Google Spreadsheets integration. If you'd use butterdb if it had that feature, please let me know.
- ejr 12y ago
  Thank you. I would use it right now actually as I do have some spreadsheets with Google. There are some I'd rather use locally like this and it would be just a nice extra. It would also avoid the need to maintain a network connection.
  - Widdershin 12y ago
    I'll definitely implement that at some point then. It's quite easy to swap out the database the model is backed by, so shouldn't be too hard.
- clxl 12y ago
  I explored this a bit (based off of the javascript-based http://sheetjs.com/sexql/ http://sheetjs.com/sexql/) but the biggest difficulty is that people use CSVs and excel files in completely different ways for the same general task. In particular, different people set up budget workbooks in very different ways. There are also input problems and invalid files to deal with, so even if you manage to craft a meaningful integration you'd still have to figure out how to determine the structure and fix subtle non-uniformities

shangxiao 12y ago

lol, when I was younger I learned that you can't use names like "fuckitdb" in front of customers / business stakeholders. Some better known software packages have also changed their names: FCKeditor, Testacular