> On 14 Feb 2019, at 22:44, Esteban Maringolo <emaring...@gmail.com> wrote:
> 
> Thank you Sven.
> 
> The timing is perfect.
> https://blog.digitalocean.com/announcing-managed-databases-for-postgresql/
> 
> :)

Interesting & cool; thanks for sharing.

> Esteban A. Maringolo
> 
> 
> El mar., 12 feb. 2019 a las 11:23, Sven Van Caekenberghe
> (<s...@stfx.eu>) escribió:
>> 
>> Hi,
>> 
>> There is a new release of P3, the modern, lean and mean PostgreSQL client 
>> for Pharo.
>> 
>> https://github.com/svenvc/P3
>> 
>> Version 1.2 contains the following changes:
>> 
>> - P3PreparedStatement is now joined by a polymorphic P3FormattedStatement 
>> working client side on text strings
>> - P3PreparedStatement & P3FormattedStatement now share the same double 
>> dispatch mechanism to process argument binding
>> - Added convenience methods #listDatabases #listSchemas & 
>> #listTablesInSchema: to P3Client
>> - Added convenience methods #firstColumnData & #firstFieldOfFirstRecord to 
>> P3Result
>> - Added dynamic ENUM support via #loadEnums in P3Client
>> - Add support for the 7 geometric types POINT, CIRCLE, LINE, LSEG, POLYGON & 
>> PATH with corresponding objects P3Point, P3Circle, P3Line, P3LineSegment, 
>> P3Polygon & P3Path
>> - Add support for the INTERVAL type with P3Interval object
>> - Added P3Client>>#serverVersion accessor
>> - Add support for BIT & VARBIT types with P3FixedBitString & P3BitString 
>> objects
>> - Add TIMETZ support
>> - Organised P3 package with tags
>> - More & better documentation & unit tests
>> 
>> https://github.com/svenvc/P3/releases/tag/v1.2
>> 
>> The quality of open source software is determined by it being alive, 
>> supported and maintained.
>> 
>> The first way to help is to simply use P3 in your projects and report back 
>> about your successes and the issues that you encounter. You can ask 
>> questions on the Pharo mailing lists.
>> 
>> Enjoy,
>> 
>> Sven
>> 
>> --
>> Sven Van Caekenberghe
>> Proudly supporting Pharo
>> http://pharo.org
>> http://association.pharo.org
>> http://consortium.pharo.org
>> 
>> 
>> 
>> 
>> 
> 


Reply via email to