Cool!
Do you know which are the changes that got harvested with the new port?
I mean, the issues fixed or the features added. An approximated
changelog would do...
-------- Original Message --------
Thanks all. There were several people that helped me along this
endeavor and I thank again the Pharo Consortium for pushing this.
2016-05-30 5:04 GMT-03:00 Denis Kudriashov <dionisi...@gmail.com>:
Good job, Esteban.
Now we need good Garage drivers for databases which not lock image. Does
anyone plan to work on Oracle and SQLServer backends?
The Garage drivers got hurt by the changes in the FFI API (UFFI), but
there are some people working on getting them back for Pharo 5. This
is really important, and for those RDBMS you mention in particular,
according to a survey [1] I did at the end of last year. We'll get
there.
That's strange. Mysql, Postgresql and Sqlite are working both for
windows and linux, pharo 4 and 5.
The only one that is not yet working is opendbx.
Is there something I'm not aware of?
Those willing to discuss issues or collaborate on these topics can
always use this mailing list, but there is an active community of
developers in the Pharo Project Slack team, we have one channel
dedicated to database discussion [2].
Also, I copied the latest commit from the SmalltalkHub repo to GitHub
in order to use its issue tracker [3] for bug reporting.
Nice!
Soon we will have git support by default in Pharo :)
Regards!
[1]
https://medium.com/@emaringolo/pharo-rdbms-support-survey-results-9c8f640878db
[2] https://pharoproject.slack.com/messages/databases/
[3] https://github.com/DBXTalk/Glorp/issues
