Re: [Pharo-users] [ANN] New Pharo Glorp version and Book chapter
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 <dionisiydk@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. 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. Regards! [1] https://medium.com/@emaringolo/pharo-rdbms-support-survey-results-9c8f640878... [2] https://pharoproject.slack.com/messages/databases/ [3] https://github.com/DBXTalk/Glorp/issues
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 <dionisiydk@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-9c8f640878... [2] https://pharoproject.slack.com/messages/databases/ [3] https://github.com/DBXTalk/Glorp/issues
2016-05-30 12:49 GMT-03:00 Guille Polito <guillermopolito@gmail.com>:
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...
I don't know, I could collect them from the Cincom Repository, I just took a look and there are over 100 commits of the Glorp bundle between 2012 and 2015. I'll perform a few queries, in Glorp, to retrieve them and summarize it wherever possible. I can easily recall changes in the Query API and features like supporting SQL's IN operator, as well as others, and support for newer versions of the platforms. One important step, is that we know which version we forked from, in the past in the Glorp mailing list happened many times they told me "use this or that" and it wasn't supported, and we didn't know how to compare feature support. Glorp lacks a good versioning strategy and just follows VW release numbers, for Pharo I decided this port will be 2.0 and use semantic versioning for future releases.
-------- Original Message --------
Thanks all. There were several people that helped me along this endeavor and I thank again the Pharo Consortium for pushing this.
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?
Pharo 4 is out of the question because it uses the old FFI. PostgreSQL and MySQL are native, so they weren't affected by FFI. But for the latest version the Garage SQLite3 driver passes its own tests (Garage ones), but when the Glorp Test suite is run with it as its driver, lots of tests fail, related with basic things of SQLite, not Glorp. I raised this concern at the beginning of this month in the #databases channel in Slack. I was delaying the release because of SQLite3 support, but couldn't wait more. However Pierce Ng (maintainer of the SQLite3 FFI driver) is working on it, but not as part of Garage AFAIU.
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 :)
I heard about it, I look forward to see it in action :) Regards!
-------- Original Message --------
2016-05-30 12:49 GMT-03:00 Guille Polito <guillermopolito@gmail.com>:
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... I don't know, I could collect them from the Cincom Repository, I just took a look and there are over 100 commits of the Glorp bundle between 2012 and 2015. I'll perform a few queries, in Glorp, to retrieve them and summarize it wherever possible.
I can easily recall changes in the Query API and features like supporting SQL's IN operator, as well as others, and support for newer versions of the platforms.
One important step, is that we know which version we forked from, in the past in the Glorp mailing list happened many times they told me "use this or that" and it wasn't supported, and we didn't know how to compare feature support.
Glorp lacks a good versioning strategy and just follows VW release numbers, for Pharo I decided this port will be 2.0 and use semantic versioning for future releases.
-------- Original Message --------
Thanks all. There were several people that helped me along this endeavor and I thank again the Pharo Consortium for pushing this. 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? Pharo 4 is out of the question because it uses the old FFI. PostgreSQL and MySQL are native, so they weren't affected by FFI. But for the latest version the Garage SQLite3 driver passes its own tests (Garage ones), but when the Glorp Test suite is run with it as its driver, lots of tests fail, related with basic things of SQLite, not Glorp. Maybe we need to enhance Garage's test suite? Can you point me to the exact cases? I raised this concern at the beginning of this month in the #databases channel in Slack. I'm not always reading slack, and sometimes I forget to open it. My linux machine does not remember opened apps as well as my old mac did :)
I was delaying the release because of SQLite3 support, but couldn't wait more. However Pierce Ng (maintainer of the SQLite3 FFI driver) is working on it, but not as part of Garage AFAIU.
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 :) I heard about it, I look forward to see it in action :)
Regards!
participants (2)
-
Esteban A. Maringolo -
Guille Polito