[SqueakDBX] Installing on Windows with MSSql backend was Re: [Esug-list] [ANN] ESUG supports once again SqueakDBX

Diogenes Moreira diogenes.moreira at gmail.com
Fri Mar 4 20:25:22 UTC 2011 

Step by Step..

For SQL Server...

1. OpenDBX use FreeTDS as backend to connect to SQLServer, please check if
TDS's dlls is in your path. (libtdsodbc-0.dll by example)
2. Please if you TDS Configuration (freetds.conf), is correct..

By Example for SQL 2005

[global]
        # TDS protocol version
tds version = 8.0
port = 1433
# Whether to write a TDSDUMP file for diagnostic purposes
# (setting this to /tmp is insecure on a multi-user system)
; dump file = /tmp/freetds.log
; debug flags = 0xffff

# Command and connection timeouts
; timeout = 10
; connect timeout = 10
 # If you get out-of-memory errors, it may mean that your client
# is trying to allocate a huge buffer for a TEXT field.
# Try setting 'text size' to a more reasonable limit
text size = 64512
May be if user debug mode (uncomment debug lines), you can get more
information.

3. If use SqueakDBX in windows please check the Enviroments Variables..
(FREETDSCONF, TDSVER).
for more detail about this backend please visit freetds site.

in SqueakDBX site[1] you can get more detailed information about how use the
diferents platform. http://www.squeakdbx.org/documentation



Best Regard

On Fri, Mar 4, 2011 at 5:01 PM, Mariano Martinez Peck <marianopeck at gmail.com
> wrote:

>
>
> On Fri, Mar 4, 2011 at 4:56 PM, Miguel Sanchez <mikey.sanchez at gmail.com>wrote:
>
>> Many thanks Mariano, copying libsybdb-5.dll to the Pharo directory
>> (along with the precompiled openDBX dll's full listing below.) sorted
>> out the problem with the DLL dialog.
>>
>>
> Excellent!  just curiosity...which country are you from?  mexico?
>
>
>> libfirebirdbackend-1.dll
>> libmssqlbackend-1.dll
>> libmysqlbackend-1.dll
>> libodbcbackend-1.dll
>> libopendbx-1.dll
>> libopendbxplus-1.dll
>> liboraclebackend-1.dll
>> libpgsqlbackend-1.dll
>> libsqlite3backend-1.dll
>> libsybasebackend-1.dll
>> libsybdb-5.dll
>>
>> However.......When I try to connect to the database (see below) I get
>> thrown into the debugger with the following signal.
>> DBXRecoverableError: RECOVERABLE OpenDBX: Connecting to server failed.
>>
>>        | conn connectionSettings |
>>    connectionSettings := DBXConnectionSettings
>>                host: 'localhost'
>>                port: '1433'
>>                database: 'LanceNG'
>>                userName: 'mike'
>>                userPassword: 'mike'.
>>
>>  conn := DBXConnection platform: DBXMSSQLPlatform new settings:
>> connectionSettings.
>>  conn connect.
>> conn open.
>>
>>
> The error sounds familiar for me. I think Diogenes had the same problem. He
> is the list and maybe he can help you.
>
>
>>
>> It's a little strange that the message occurs on "conn open" and not
>> on "conn connect" (?).
>
>
> That's correct. In most databases, connect only opens the TCP/IP connection
> to the host:port. And then the #open logs in the database, using the databae
> name, username, and passwd.
>
>
>> I have tested the user from the local MSSQL
>> management Studio and logs in fine and has correct permissions on
>> objects. I have not found a dump or debug log in the Pharo directory.
>>
>> I'll start looking at compiling freetds and opendbx as there may be
>> utilities that will give more meaningful debug info to isolate where
>> the problem lies.
>>
>
> did you try connecting througt TSQL? does it work?
>
> cheers
>
> mariano
>
>
>>
>> Best Regards,
>>
>>
>> Miguel
>>
>>
>>
>>
>>
>> On 4 March 2011 10:39, Mariano Martinez Peck <marianopeck at gmail.com>
>> wrote:
>> > Hi. I cc'ed the squeakdbx mailing list because others may help you
>> better
>> > than me. You can register if you want.
>> >
>> > On Fri, Mar 4, 2011 at 10:26 AM, <Mikey.Sanchez at gmail.com> wrote:
>> >>
>> >> Buenos dias (tardes?)
>> >>
>> >
>> > jejeje buenos días acá (estoy en Francia ahora)
>> >
>> >>
>> >> That's brilliant news! In enterprise legacy DB's are (still) so often
>> the
>> >> simplest integration point that a functional non-blocking
>> implementation is
>> >> vital.
>> >>
>> >> By coincidence I've been looking at SqueakDBX to interface to a
>> SQLServer
>> >> database for a once off import (for now) using Pharo 1.1.1 one-click.
>> >> and......... I'm having some trouble.
>> >> I installed SqueakDBX and Glorp via metacello.
>> >> Downloaded Windows binaries for openDBX.
>> >> Got a windows dialog when trying to connect that libsybdb-5.dll was
>> >> missing.
>> >> Soooooo when I googled it I came to the conclusion that I need to
>> compile
>> >> either openDBX or freeTDS. However mingw.org seems to be out of action
>> and
>> >> I'm struggling to find alternative installers.
>> >>
>> >
>> > All that is true. Whenever you want to use SqueakDBX you need both:
>> openDBX
>> > library AND the database client library. However, there are already
>> copiled
>> > dll so that you can directly use.
>> >
>> >>
>> >> While googling I saw that you had responded to newbies in the squeakDBX
>> >> mailing list making suggestions. You wouldn't happen to know where I
>> can lay
>> >> my hands on a compiled 32 bit libsybdb-5.dll. It would save me some
>> pain I
>> >> think .
>> >
>> > Sure. I attach. Please rename .xxx to .dll
>> > Now, I wondering if we should upload them for make it easier...
>> >
>> > BTW, these links should help you in case you need to compile:
>> >
>> > http://www.squeakdbx.org/SQL%20Server
>> > http://www.squeakdbx.org/database%20scripts
>> > http://www.squeakdbx.org/SQL%20Server%20for%20Win
>> >
>> >>
>> >> BTW. What is the state of squeakDBX W.R.T. MSSQL at the moment?
>> >>
>> >
>> > It is working. In fact, Diogenes Moreira did a production system using
>> > GLorpDBX + SqueakDBX + MSSQL
>> >
>> > cheers
>> >
>> > mariano
>> >
>> >>
>> >> Many thanks.
>> >>
>> >>
>> >> Miguel Sanchez
>> >>
>> >>
>> >> On Mar 4, 2011 9:40am, Mariano Martinez Peck <marianopeck at gmail.com>
>> >> wrote:
>> >> > We are really happy to announce that ESUG
>> >> > will sponsor us once again through the ESUG Summer Talk project. This
>> >> > means
>> >> > that we have reached the ESUG expectations and that they still think
>> >> > that relational database access is an important matter in Smalltalk.
>> >> >
>> >> >
>> >> >
>> >> > One important thing is that we are going to rename the project (we
>> >> > are still working on it) since SqueakDBX runs not only in Squeak but
>> >> > also in Pharo, and there have been even ports to Dolphin. What's the
>> >> > reason for this decision? Because we do not want to couple ourselves
>> to
>> >> > a
>> >> > smalltalk dialect nor to OpenDBX, because our project is much more
>> than
>> >> > that (later I will tell you about our plans). So, these are some of
>> the
>> >> > possible names: ObjectPark, SmallParking, Parktalk, SmallValet,
>> >> > Valetalk, ValetST, NorayTalk, Ballard, Noray and Cruise. Please let
>> us
>> >> > know which one is your favourite or help us find a new one.
>> >> >
>> >> >
>> >> >
>> >> > Another important subject is the team. There will be three
>> >> > "mentors", Esteban Lorenzano, Diogenes Moreira and myself, Mariano
>> >> > Martinez Peck; and three students: Guillermo Polito, Nicolas
>> Scarcella
>> >> > and Santiago Bragagnolo.
>> >> >
>> >> >
>> >> >
>> >> > We are open to suggestions and ideas. In addition, we have defined a
>> >> > possible list of actions that I copy at the end of the email.
>> >> >
>> >> > For the moment, the url remains www.squeakdbx.org and the mailing
>> >> > list squeakdbx at lists.squeakfoundation.org
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > Once again, we want to thank ESUG for their support and trust.
>> >> >
>> >> > Thank
>> >> > you very much,
>> >> >
>> >> > SqueakDBX team
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > Possible
>> >> > list of actions:
>> >> >
>> >> > 1) Change SqueakDBX’s name.
>> >> >
>> >> > 2)
>> >> > Update GLORP version since the actual one is 3 years old.
>> >> >
>> >> >
>> >> >
>> >> > Port it again from VisualWorks, create a VW porting tool (may be).
>> >> > Complete
>> >> > support to Glorp.  Today it works with PostgreSQL, Oracle and MySQL.
>> >> >  Make it work with most databases OpenDBX supports.
>> >> >
>> >> > 3) Create a
>> >> > lightweight solution, alternatively to GLORP.  There are some
>> options:
>> >> >
>> >> >
>> >> >
>> >> > Make SqueakSave work with SqueakDBX.  SqueakSave developers already
>> >> > contacted us because they wanted to do it. SqueakSave seems to be 20%
>> >> > slower than Glorp but you don't need to write the mappings :)
>> >> > Adapt
>> >> > Ramon Leon's active record to use an abstract database driver, and
>> >> > create a driver for SqueakDBX.
>> >> >
>> >> >
>> >> > Port the new Glorp’s kind of active record to Pharo. (included in 2).
>> >> >
>> >> > 4)
>> >> > Write a Pharo By Example 2 chapter based on the card game Stef built
>> >> > ;).
>> >> >
>> >> > 5) Cog compatibility.
>> >> >
>> >> > 6) Use Alien instead of FFI.
>> >> >
>> >> >
>> >> > Eliot is working on a threaded CogVM. One of the projects of the GSoC
>> of
>> >> > this year was to make something similar to a threaded FFI. What the
>> >> > student did is a modification in Alien (I think) that can be run in a
>> >> > multithreaded envirorment. He worked with Eliot. The idea is when
>> Eliot
>> >> > releases the threaded CogVM, this FFI would work our of the box, and
>> >> > would avoid locking the WHOLE vm while a C function is being invoked
>> (as
>> >> > it happens today with FFI).....So....when that VM is released, we
>> MUST
>> >> > migrate to that).
>> >> >
>> >> >
>> >> >
>> >> > 7) Explore performance issues (maybe with our approach of "In thread
>> >> > execution plugin").
>> >> >
>> >> >
>> >> > 8) Complete integration with OpenDBX.
>> >> > For example, Oracle, for large objects (Clob, Blob, etc) use specific
>> >> > functions. There are specific functions in OpenDBX that have to be
>> used
>> >> > if the database uses specific functions (oracle is the only one for
>> the
>> >> > moment.). We don't manage those functions yet.
>> >> >
>> >> >
>> >> >
>> >> > 9) In this link http://www.squeakdbx.org/Targets%20and%20Features
>> >> > You
>> >> > can see a list of future possible features like Connection pooling
>> (now
>> >> > it is done!), Prepared statement interface, Store procedures, Escape
>> >> > and avoid of SQL insertion, Authentication support: extends to other
>> >> > methods, not only user/password, Full text support, etc.
>> >> >
>> >> >
>> >
>> _______________________________________________
>> SqueakDBX mailing list
>> SqueakDBX at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx
>>
>
>
> _______________________________________________
> SqueakDBX mailing list
> SqueakDBX at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeakdbx/attachments/20110304/ccd2754d/attachment.htm

More information about the SqueakDBX mailing list