[Pharo-project] Persistence options
Hi, there are various options for persistence in Pharo and Seaside. What do people use for their applications? Any experiences or numbers to share? I'm interested in both, mainly with the focus on options for RDBM systems. Whats is the state of Glorp? Thx T. -- NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone! Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a
I've been using Glrop for 3 weeks now (not much I know) to link an existing application data model to an existing RDMS model with all sorts of weird mappings and it works fine. Several times I have started to write patches but it turned out it was a problem in my code. Diagnostics could be better. This same app was running on Magma (never in production) and it also worked like a charm, If you don't mind your data being stored in some format no one else can read. On 25 June 2012 21:41, Torsten Bergmann <astares@gmx.de> wrote:
Hi,
there are various options for persistence in Pharo and Seaside.
What do people use for their applications? Any experiences or numbers to share?
I'm interested in both, mainly with the focus on options for RDBM systems. Whats is the state of Glorp?
Thx T. -- NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone! Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a
-- Milan Mimica http://sparklet.sf.net
I have been using goods in production with 3 images banging away at it on Pharo 1.3. It has been working well. (Some days it fires out over 50K emails/sms/apple push notifications so it is reasonbly significant under load) I run a daily backup of the database using an expect script. I am having problems upgrading to Pharo 1.4 but I think that this is just my problem that i need to address. S. On Jun 26, 2012, at 2:22 PM, Milan Mimica wrote:
I've been using Glrop for 3 weeks now (not much I know) to link an existing application data model to an existing RDMS model with all sorts of weird mappings and it works fine. Several times I have started to write patches but it turned out it was a problem in my code. Diagnostics could be better. This same app was running on Magma (never in production) and it also worked like a charm, If you don't mind your data being stored in some format no one else can read.
On 25 June 2012 21:41, Torsten Bergmann <astares@gmx.de> wrote: Hi,
there are various options for persistence in Pharo and Seaside.
What do people use for their applications? Any experiences or numbers to share?
I'm interested in both, mainly with the focus on options for RDBM systems. Whats is the state of Glorp?
Thx T. -- NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone! Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a
-- Milan Mimica http://sparklet.sf.net
On 25 Jun 2012, at 21:41, Torsten Bergmann wrote:
I'm interested in both, mainly with the focus on options for RDBM systems. Whats is the state of Glorp?
If have been using Glorp with Postgresql and it works surprisingly well. It is 'good old technology', not as sexy as all this NoSQL stuff, but reliable, well-known. I think that Glorp is one of the coolest OO-RDBMS mappers around, in any language. Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill
while a lot of years of suffering are clamming that I need to say: "don't use RDBMs if you can avoid it", I also should point you to http://dbxtalk.smallworks.com.ar/, and GlorpDbx which is around and is the newer port to Pharo you can find :) Esteban On Jun 26, 2012, at 8:53 AM, Sven Van Caekenberghe wrote:
On 25 Jun 2012, at 21:41, Torsten Bergmann wrote:
I'm interested in both, mainly with the focus on options for RDBM systems. Whats is the state of Glorp?
If have been using Glorp with Postgresql and it works surprisingly well. It is 'good old technology', not as sexy as all this NoSQL stuff, but reliable, well-known. I think that Glorp is one of the coolest OO-RDBMS mappers around, in any language.
Sven
-- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill
Not being Glorp's author, I can tell it has over 600 green tests on pharo. Of course it can have it's problems, but you have some confidence it is ok, and some sources for examples :). On Tue, Jun 26, 2012 at 9:43 AM, Esteban Lorenzano <estebanlm@gmail.com>wrote:
while a lot of years of suffering are clamming that I need to say: "don't use RDBMs if you can avoid it", I also should point you to http://dbxtalk.smallworks.com.ar/, and GlorpDbx which is around and is the newer port to Pharo you can find :)
Esteban
On Jun 26, 2012, at 8:53 AM, Sven Van Caekenberghe wrote:
On 25 Jun 2012, at 21:41, Torsten Bergmann wrote:
I'm interested in both, mainly with the focus on
options for RDBM systems. Whats is the state of Glorp?
If have been using Glorp with Postgresql and it works surprisingly well. It is 'good old technology', not as sexy as all this NoSQL stuff, but reliable, well-known. I think that Glorp is one of the coolest OO-RDBMS mappers around, in any language.
Sven
-- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill
participants (6)
-
Esteban Lorenzano -
Guillermo Polito -
mail list -
Milan Mimica -
Sven Van Caekenberghe -
Torsten Bergmann