On Jul 11, 2013, at 3:52 PM, Mariano Martinez Peck
wrote:
> I do agree. But notice that it took me like 2 days to adapt the pool to the
> native driver, find the problems, fix the bugs, commit fixed, update the
> confs, etc.
> So that was already something :)
Indeed :)
Stef
>
>
> On Thu,
I do agree. But notice that it took me like 2 days to adapt the pool to the
native driver, find the problems, fix the bugs, commit fixed, update the
confs, etc.
So that was already something :)
On Thu, Jul 11, 2013 at 4:14 AM, Stéphane Ducasse wrote:
>
> On Jul 10, 2013, at 10:04 PM, Mariano Ma
On Jul 10, 2013, at 10:04 PM, Mariano Martinez Peck
wrote:
> Hi guys
>
> I did a couple of things related to Glorp. I commited 2 fixes related to the
> connection pool.
> Also, for the native postgres driver, I adapted the pool we have for
> OpenDBXDriver. It's quite ugly because we are dupl
If by PostgresSQL you mean the native driver (not OpenDBXDriver), then in
my conf I load from '
http://www.smalltalkhub.com/mc/DBXTalk/Configurations/main'
(ConfigurationOfGlorpDBX project version: '2.8') load:
#('GlorpPostgresV2NativeWithTests' ).
That should work.
On Thu, Jul 11, 2013 at 9:2
What is the configuration I should load to get the latest Glorp + PostgreSQL?
Esteban A. Maringolo
2013/7/10 Mariano Martinez Peck :
> Hi guys
>
> I did a couple of things related to Glorp. I commited 2 fixes related to the
> connection pool.
> Also, for the native postgres driver, I adapted the
Hi guys
I did a couple of things related to Glorp. I commited 2 fixes related to
the connection pool.
Also, for the native postgres driver, I adapted the pool we have for
OpenDBXDriver. It's quite ugly because we are duplicating quite a lot of
code, but the hierarchy make things complicated here a
