Hi all, We have been using ReStore[1] as a lightweight approach to data persistence and ODBC handing form Pharo/GT with pretty good results, as can be showcased in our #CandidatosEnDatos (candidates in data) project [1a]. [1] https://github.com/rko281/ReStoreForPharo [1a] https://mutabit.tiddlyhost.com/#CandidatosEnDatos The microwiki is in Spanish, but there are some data storytelling and visualization we did regarding the candidates for the past presidential elections in Colombia (screenshot below and you can zoom them and fine others in the site linked above). We used ReStore as the database backend to store and query around 10 thousand tweets for over a month from all the presidential candidates in Colombia a store them in a SQLite database. Then we made several visualizations and inject them using Norbert's excellent Mustache for Pharo into a LaTeX template to produce the data visualizations as high definition PNGs. ReStore worked more than well, helping us with all the object-relational mapping and migration, with just some desired features we would like to have but any deal breaker and we didn't find any problem with our SQLite backend regarding performance or size of the information we wanted to work with. I know that ReStore has support for other database engines. Unfortunately I had to cancel my participation to this year ESUG, so I wont be able to share more details about this and other projects I was showcasing there. And maybe a project about data storytelling and visualization for civic tech is pretty far away of most use cases where a Object-relational mapper is needed... or maybe not and this combination could work for other people too. I'll be happy to share more details if that the case. Enjoy ESUG and hopefully we will find soon in virtual events or next year in ESUG. Cheers, Offray On 9/08/22 5:20, Norbert Hartl wrote:
Hi Dale,
thanks for the pointer. Â I always admired what the GemStone people did and do. But I'm looking for something more lightweight and more easy to handle approach this time. Well, from the github page I could not derive what it really does to be honest.
Hope to see you at ESUG,
Norbert
Am 08.08.2022 um 18:44 schrieb Dale Henrichs <dale.henrichs@gemtalksystems.com>:
Norbert, Before you go off and invent a data base, you might take a look at GemStone and RemoteServiceReplication[1] ...
Dale
[1] https://github.com/GemTalk/RemoteServiceReplication
On Mon, Aug 8, 2022 at 6:19 AM Norbert Hartl <norbert@hartl.name> wrote:
To all Omnibase and Monibase users.
It turned out that neither of those are open source. The author of the database contacted me clarifying the situation that he has the copyright and never released something open source. This means that I will remove the Omnibase repositories in few weeks from
https://github.com/ApptiveGrid/MoniBase
and
https://github.com/pharo-nosql/OmniBase
I'm very sorry about that but someone just took the code 9 years before, copied it on github and put illegally an MIT license to the repository. We only want free software in our repositories and hence the above will go away.
As we see it essential to have a good OO database in pharo we will see how much effort it will be build a small and simple OO database that can replace Omnibase.
regards,
Norbert
