[ANN] CouchDB Client for Pharo
Hello all, I finished polishing the repository a CouchDB client for Pharo that I forked from an old, and seemingly abandoned, client for VisualWorks. I took that code and refactored heavily to use Pharo and Zinc core classes, and that included renaming the client classes, methods and the strategy used to map objects to/from JSON. It is available at: https://github.com/eMaringolo/pharo-couchdb I'm open to questions or suggestions about this or how to use it. Disclaimer: This is mostly experimental since I'm not using it in production and was done as a means of exploration of CouchDB itself for a project I'm prospecting. There are a lot of features that could be added to the client, and things that could be refactored further (such as the class side request methods), but adding that is simple, and the current state provides almost feature complete coverage. Best regards, Esteban A. Maringolo
Well... I wasn't aware such client existed. #facepalm Looking at it, it seems to fulfill the pending features I was talking about, including the option to use Pharo as a View server! (running map/reduce operations) and the Mango Queries (it's not a typo of Mongo, it's a different thing [1]). It is certainly more complete, but also heavier and more complex to use for simple operations. In any case I added a link to it in the README.md of my repository for those looking for the missing parts. Thank you! [1] https://github.com/cloudant/mango Esteban A. Maringolo El mié., 13 mar. 2019 a las 4:30, Torsten Bergmann (<astares@gmx.de>) escribió:
Nice. How does it relate/compare to https://github.com/jmari/SCouchDB ?
*Gesendet:* Mittwoch, 13. März 2019 um 03:18 Uhr *Von:* "Esteban Maringolo" <emaringolo@gmail.com> *An:* "Pharo users" <pharo-users@lists.pharo.org> *Betreff:* [Pharo-users] [ANN] CouchDB Client for Pharo Hello all,
I finished polishing the repository a CouchDB client for Pharo that I forked from an old, and seemingly abandoned, client for VisualWorks.
I took that code and refactored heavily to use Pharo and Zinc core classes, and that included renaming the client classes, methods and the strategy used to map objects to/from JSON.
It is available at: https://github.com/eMaringolo/pharo-couchdb
I'm open to questions or suggestions about this or how to use it.
Disclaimer: This is mostly experimental since I'm not using it in production and was done as a means of exploration of CouchDB itself for a project I'm prospecting.
There are a lot of features that could be added to the client, and things that could be refactored further (such as the class side request methods), but adding that is simple, and the current state provides almost feature complete coverage.
Best regards,
Esteban A. Maringolo
Cool! I added an entry [1] for it to awesome-pharos [2]. Cheers, Julien Links: [1]: https://github.com/pharo-open-documentation/awesome-pharo/pull/56 [2]: https://github.com/pharo-open-documentation/awesome-pharo --- Julien Delplanque Doctorant à lâUniversité de Lille http://juliendelplanque.be/phd.html Equipe Rmod, Inria Bâtiment B 40, Avenue Halley 59650 Villeneuve d'Ascq Numéro de téléphone: +333 59 35 86 40
Le 13 mars 2019 à 03:18, Esteban Maringolo <emaringolo@gmail.com> a écrit :
Hello all,
I finished polishing the repository a CouchDB client for Pharo that I forked from an old, and seemingly abandoned, client for VisualWorks.
I took that code and refactored heavily to use Pharo and Zinc core classes, and that included renaming the client classes, methods and the strategy used to map objects to/from JSON.
It is available at: https://github.com/eMaringolo/pharo-couchdb <https://github.com/eMaringolo/pharo-couchdb>
I'm open to questions or suggestions about this or how to use it.
Disclaimer: This is mostly experimental since I'm not using it in production and was done as a means of exploration of CouchDB itself for a project I'm prospecting.
There are a lot of features that could be added to the client, and things that could be refactored further (such as the class side request methods), but adding that is simple, and the current state provides almost feature complete coverage.
Best regards,
Esteban A. Maringolo
I could not see an entry for Voyage here. Am I missing seeing it. On Wed 13 Mar, 2019, 1:39 PM Julien, <julien.delplanque@inria.fr> wrote:
Cool!
I added an entry [1] for it to awesome-pharos [2].
Cheers,
Julien
Links: [1]: https://github.com/pharo-open-documentation/awesome-pharo/pull/56 [2]: https://github.com/pharo-open-documentation/awesome-pharo
--- Julien Delplanque Doctorant à lâUniversité de Lille http://juliendelplanque.be/phd.html Equipe Rmod, Inria Bâtiment B 40, Avenue Halley 59650 Villeneuve d'Ascq Numéro de téléphone: +333 59 35 86 40
Le 13 mars 2019 à 03:18, Esteban Maringolo <emaringolo@gmail.com> a écrit :
Hello all,
I finished polishing the repository a CouchDB client for Pharo that I forked from an old, and seemingly abandoned, client for VisualWorks.
I took that code and refactored heavily to use Pharo and Zinc core classes, and that included renaming the client classes, methods and the strategy used to map objects to/from JSON.
It is available at: https://github.com/eMaringolo/pharo-couchdb
I'm open to questions or suggestions about this or how to use it.
Disclaimer: This is mostly experimental since I'm not using it in production and was done as a means of exploration of CouchDB itself for a project I'm prospecting.
There are a lot of features that could be added to the client, and things that could be refactored further (such as the class side request methods), but adding that is simple, and the current state provides almost feature complete coverage.
Best regards,
Esteban A. Maringolo
participants (4)
-
Esteban Maringolo -
Julien -
Sanjay Minni -
Torsten Bergmann