On Thu, Oct 13, 2011 at 1:56 PM, jtuchel@objektfabrik.de <jtuchel@objektfabrik.de> wrote:
Hi,

DBXTalk is good work!
I really love to see that stuff going forward!


Thanks.
Before I spend a lot of time playing around: has anybody tried using Pharo/GLORP/ODBC (Access or SQLSrv) on Windows?

Yes, but I have to admit that it's almost the most complicated scenario to configure. At least I know someone tried Pharo/Glorp/ODBC/SQL Server.
I think you can just give it a try. Get the dll of OpenDBX (they are in our website), get a Pharo VM that has a working FFI, and give it a try.
Or Pharo/GLORP/SQLite on Windows?

Yes, this works almost out of the box. In fact, I can provide you a zip that contains Pharo VM + image + opendbx dll + sqlite dll.
Is there some place on the web where I can find info on how to set this up?


http://dbxtalk.smallworks.com.ar/Compiling%20and%20installing%20OpenDBX
http://dbxtalk.smallworks.com.ar/Compiling%20for%20different%20backends

In an open source context, this is probably a heretic question, and if I could choose freely, Linux and PostgresQL would be my favorite.

Sure, that's pretty easy. OpenDBX and PostgreSQL are easy to make it work in Linux.
OTOH: The fact that each windows installation comes with an Access engine and respective ODBC driver makes the combination very attractive for starting something on a windows machine really fast. No installation of anything but Pharo, no need for admin rights or anything. Just set up the odbc driver and off you go! Great chance to show the strength of Smalltalk and Glorp to other team members and friends...

well more or less. In the case of DBX you will need the OpenDBX library anyway, even if being ODBC. OpenDBX sees ODBC just as another backend. And of course, that's only if you like accessing by ODBC (which I don't like BTW).� Of course, you can create a database driver for Glorp that uses the ODBC driver of squeak in which case you wouldn't need the OpenDBX driver.
SQLite is a similar story: copy the dlls onto the machine and the journey can start.


yes, that's even easier. As I say, it can be provided in a "DBXOneClick" :)


Cheers

--
Mariano
http://marianopeck.wordpress.com