[Raion]

Postgres is not overly object oriented. SQL is mostly SQL which is why porting between engines is not difficult.

[vishnu]

Postgres is not overly object oriented. SQL is mostly SQL which is why porting between engines is not difficult.

I agree, it's like C++, people have always complained that C++ falsely claims to be an object-oriented language, but Bjarne Stroustrup has said, at least a million times, that it's not an object oriented language, it's a language with features that support object oriented programming. That's why he originally called it "C with classes." Postgres is the same thing, you can use it as a row and column SQL database, or as an object-relational database. I've never used it, but everything I've ever heard about it has been pretty positive. 😁

[jpstewart]

Postgres is the same thing, you can use it as a row and column SQL database, or as an object-relational database. I've never used it, but everything I've ever heard about it has been pretty positive. 😁

I've been using Postgres for nearly 20 years now and have never once used or needed its object-relational aspects. As a plain SQL database, I find it to be reliable and easy to use. I'm sure Raion will be happy with it if the migration hassles can be overcome.

I started using Postgres at a time when MySQL didn't support certain features (foreign keys and transactions, IIRC) which were critical for another piece of open source software which I needed to run on top of a database. Postgres was the only open source database they supported at the time -- along with IBM DB2 and Oracle which were obviously well out of my price range! So I kind of got forced into Postgres and have never used MySQL (or its descendants). But I've also never regretted the choice of Postgres. Once I had it running for that one piece of third-party software I used it for all my personal needs and development work. Since 2003!

[Raion]

I just know it's gonna have to happen. Right now anothnr thing I'm discussing with the various web devs is the adoption of some kind of database abstraction library so that we can rewrite our plugins in place and then simply migrate them over.

But at this moment it's a lot of research, as I said above I put this on hold. There's currently too much at stake to rush into it so I'll wait until after we have the gallery done which is running behind due to cash flow issues. I was planning to have the group buy by now, but logistics keep getting gummed up. I had to go back to our manufacturer for a third time because of our sample shipment getting lost/stolen. Until I'm satisfied with the samples and have the ability to take photos for Shopify or whatever we're gonna use, I want to hold off. Gotta make sure this is a real and tangible thing to our users.