I tend to agree with you. I like SQLite. Also, MongoDB isn't bad, either. But is there no scenario where an OODB would be highly advantageous? tblanchard wrote
Just out of curiosity, why do you want an OODB?
SQLite has a plethora of tools, powerful query capabilities, can be migrated with very little pain, and can act a bit like an OODB using GLORP.
I have lost too many data sets to proprietary OODBs to ever trust one again.
On May 6, 2018, at 10:00 AM, horrido <
horrido.hobbies@
> wrote:
Just out of curiosity, which object database is recommended for Pharo? Something that is reliably up-to-date as Pharo changes.
Stephan Eggermont-3 wrote
Sean P. DeNigris <
sean@
> wrote:
OT: It's ironic that Smalltalkers are often accused of NIH syndrome, but the first reaction of people from less "productive" languages/systems is to rewrite a working Smalltalk app in their language of comfortâ¦
Indeed. And rewriting something that also uses an OODB is going to kill productivity even more. Iâve taken a look at what would be needed to support magma on pharo a few years ago. Chris always told us he uses it professionally on squeak and has not enough capacity to keep up with changes in pharo without having a customer/maintainer for it. Twice a year or so someone asks about magma on pharo and takes a look. AFAIK there are no real obstacles to a port, but magma uses a lot of deep implementation specifics that will take an experienced smalltalker to deal with, and a lot of mailing list archeology as pharo changed a lot since magma worked on pharo last
Stephan
-- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html>;
-- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html