3 ms·

You could have easily done that with a single file with a tail header for look ups.

baq 5y ago
Easier than SQLite? With less bugs and better tests? SQLite advertises itself as an fopen replacement. Sounds like a perfect match for parent’s use case.
- KerrAvon 5y ago
  Depends on the indexing needs, right? Something like IFF should be fine if you need a sequence of images to store that you don’t need to actually query for individually.
  - baq 5y ago
    Always, but I find it really hard to see how not using SQLite in this use case is the better option. Maybe if you need every single percentile of performance? In 99% of other cases just go with SQLite.
- jbluepolarbear 5y ago
  Yes easier, as in time to integrate and get working correctly. I’ve used SQLite extensively over the last 10 years and yes it’s a good solution, but not a replacement for fopen. A flat file would be easier to integrate, test, and harden over SQLite. Would take about the same time as integrating SQLite into a system for the same purpose and would be easily extendable to support features as the system grows.
  - ehvatum 5y ago
    > Would take about the same time as integrating SQLite into a system for the same purpose and would be easily extendable to support features as the system grows. I find it much easier to add features to my post-2007 projects (when I started using SQLite) for the specific reason that I can open the SQLite file in a GUI and pretty quickly see what’s going on with data organization (schema) and how the customer uses the software I wrote (ie by what columns they actually use/misuse). Prior to that, there’s various versions of my b-tree library and lots of zips, or linear text indexes, or any combination of whatever fit the need. Data storage implementation needs to be reasoned about in detail for each pre-2007 revisit in ways that don’t happen with SQLite projects.
    - heinrich5991 5y ago
      What's the UI you use for viewing SQLite files?
      - ehvatum 5y ago
        At client site to debug issues and deal with things like bulk product name changes https://sqlitebrowser.org/ https://sqlitebrowser.org/ For more involved work that I do at my shop or on my laptop, DataGrip by Jet Brains is great. Before I got fed up with Apple, I used https://menial.co.uk/base/ https://menial.co.uk/base/ DataGrip’s benefit to me is mainly reworking a customer DB at the ER diagram level, then I manually update my code to match.
      - ehvatum 5y ago
        By the way, SQLite started out as a TCL extension. It works really well in TCL and good old TCL/TK/SQLite gets CRUD done fast. I almost feel bad looking so heroic.
electroly 5y ago
I'm aware; I mentioned this at the end of my post. This is still easier. I want to clearly express how absolutely trivial it was to use SQLite for this. I didn't really have to think about anything.

baq 5y ago

Easier than SQLite? With less bugs and better tests? SQLite advertises itself as an fopen replacement. Sounds like a perfect match for parent’s use case.

KerrAvon 5y ago
Depends on the indexing needs, right? Something like IFF should be fine if you need a sequence of images to store that you don’t need to actually query for individually.
- baq 5y ago
  Always, but I find it really hard to see how not using SQLite in this use case is the better option. Maybe if you need every single percentile of performance? In 99% of other cases just go with SQLite.
jbluepolarbear 5y ago
Yes easier, as in time to integrate and get working correctly. I’ve used SQLite extensively over the last 10 years and yes it’s a good solution, but not a replacement for fopen. A flat file would be easier to integrate, test, and harden over SQLite. Would take about the same time as integrating SQLite into a system for the same purpose and would be easily extendable to support features as the system grows.
- ehvatum 5y ago
  > Would take about the same time as integrating SQLite into a system for the same purpose and would be easily extendable to support features as the system grows. I find it much easier to add features to my post-2007 projects (when I started using SQLite) for the specific reason that I can open the SQLite file in a GUI and pretty quickly see what’s going on with data organization (schema) and how the customer uses the software I wrote (ie by what columns they actually use/misuse). Prior to that, there’s various versions of my b-tree library and lots of zips, or linear text indexes, or any combination of whatever fit the need. Data storage implementation needs to be reasoned about in detail for each pre-2007 revisit in ways that don’t happen with SQLite projects.
  - heinrich5991 5y ago
    What's the UI you use for viewing SQLite files?
    - ehvatum 5y ago
      At client site to debug issues and deal with things like bulk product name changes https://sqlitebrowser.org/ https://sqlitebrowser.org/ For more involved work that I do at my shop or on my laptop, DataGrip by Jet Brains is great. Before I got fed up with Apple, I used https://menial.co.uk/base/ https://menial.co.uk/base/ DataGrip’s benefit to me is mainly reworking a customer DB at the ER diagram level, then I manually update my code to match.
    - ehvatum 5y ago
      By the way, SQLite started out as a TCL extension. It works really well in TCL and good old TCL/TK/SQLite gets CRUD done fast. I almost feel bad looking so heroic.

electroly 5y ago

I'm aware; I mentioned this at the end of my post. This is still easier. I want to clearly express how absolutely trivial it was to use SQLite for this. I didn't really have to think about anything.