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