Hi Stephan, Very interesting !
It would be good to switch from the textual V2 protocol to the binary V3, not only is it faster (or should it be faster), it has more features and it is more modern (ie. the way forward). Do you think is would make sense to separate the different layers (or maybe this is already the case) ? The code mirroring should be optional as it has much more dependencies. We should definitively talk about this during the Pharo Days ! Sven > On 10 Jan 2015, at 10:59, Stephan Eggermont <step...@stack.nl> wrote: > > Stef wrote: >> May be this is the time to improve this package :) >> I'm sorry I have no DB experience. >> As part of the consortium agenda for this year we have >> - better ffi >> - better db support > > Moving to Levente's PostgreSQLv3 and migrating that > might be a better idea. He has been using it in production > systems for a long time AFAIK. > > The code mirror is very interesting. Porting it needs > someone with close access to Opal/old compiler knowledge. > The way it works now in Squeak looks ideal for someone > with a PostgreSQL background. Using a code browser > to edit plsql, and having a directly mirrored smalltalk > class for each table. > > http://forum.world.st/Status-of-PostgresV3-td4780110.html > I have verified that the connection works and that I can get > data out of postgres. > Missing: > - switch the code highlighter from smalltalk to one > for plsql in nautilus. > - connect to glorp > - (later) add a real plsql parser (petitsql?) > > Stephan > >
