> On 27 Jun 2017, at 17:37, Michael Forster <[email protected]> wrote: > > On Tue, Jun 27, 2017 at 7:56 AM, Sven Van Caekenberghe <[email protected]> wrote: >> P3 is a modern, lean and mean PostgreSQL client for Pharo. >> >> P3Client uses frontend/backend protocol 3.0 (PostgreSQL version 7.4 [2003] >> and later), implementing the simple query cycle. It supports plaintext and >> md5 password authentication as well as SSL connections. When SQL queries >> return row data, incoming data is efficiently converted to objects. P3Client >> supports most common PostgreSQL types. >> >> With P3DatabaseDriver, an interface between Glorp, an advanced >> object-relational mapper, and P3Client, most Glorp unit tests pass (the same >> number as the older, proven PostgresV2 driver, that is using the legacy 2.0 >> protocol). This was the initial design goal. >> >> More info, usage examples and code at https://github.com/svenvc/P3 >> >> P3 is written in pure Pharo, using a TCP network connection to PostgreSQL. >> >> This is an alpha release for the brave of heart that needs more real world >> testing before it is ready for general release. >> >> Sven >> >> PS: I wrote this using 64-bit Pharo 6 on macOS using the Calypso browser and >> it was a beautiful & satisfying experience. Thank you Denis, well done ! I >> also used Iceberg a second time and it starts to feel natural to me. Thank >> you Nico and Esteban ! >> >> > > > Very nice, Sven. Common Lisp's loss was Pharo's gain ;-)
Haha, my CL days are long, long gone (though I still maintain 1 CL web app in production, more than 10 years after it was written), but it was a lot of fun. Like Common Lisp, I feel that Pharo is really an amplifier, a power tool, that makes seemingly impossible things possible and easy/fun to do. If you look at all the code being written by others (Calypso, Iceberg, Epicea, GT Tools, Spotter, and so many, many others), you can see the same effect going on. What is important IMHO is that people stick with (keeping supporting/documenting/promoting) the open source code they publish (else it will decay very quickly). > Mike >
