SqueakDBX April 2011

squeakdbx@lists.squeakfoundation.org

6 participants
6 discussions

MSSQL, selecting nvarchar (other types too) field causes DBXTypeNotSupported.
by Miguel Sanchez 05 May '11

05 May '11

OK thanks guys I'll answer answer both in one shot. > Date: Fri, 29 Apr 2011 10:54:37 +0200 > From: Mariano Martinez Peck <marianopeck(a)gmail.com> > Subject: Re: [SqueakDBX] MSSQL, selecting nvarchar (other types too) > field causes DBXTypeNotSupported. > To: The complete and open-source solution to relational database > access <squeakdbx(a)lists.squeakfoundation.org> > Message-ID: <BANLkTi=jeTSo2UOvchsyc=Mp=WbRtfRVxw(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi Miguel. This is something that we really need to fix and make it clear. My apologies for the newbie questions and generally being dense about understanding the code. > > I will try to explain: OpenDBX library have 4 special functions (check > above in http://www.linuxnetworks.de/doc/index.php/OpenDBX/C_API/1.2) when > managing large objects WHEN the backend requires such. > We wrongly understood that at the beginning. So...we throw > DBXTypeNotSupported for every large object even if we could really support > it. .... and this includes nvarchar? This doesn't need the large object functiuon calls does it? doesn't really matter. If it's assigned unknown then it needs to be handled anyway. > > So...a backend, i.e, a database client library, 1) can support large objects > with the regular functions (like regular fields); 2) or need special > functions to manage them (and hence, use the special functions of OpenDBX). > We ONLY support 1) since we didn't yet wrap the OpenDBX functions for large > objects. However, only Firebird is using those functions for large > objects. ALL the rest of the backends, use 1), so we should support it. > > Now...what is the problem? as I told you, we misunderstood that and > therefore we directly throw DBXTypeNotSupported for every large object. > Take a look to DBXPlatform class >> createDataTypesMap > Now, "some" were already fixed. For example, createDataTypesMap overwrites > #createDataTypesMap and fixes Clob and Blob. > Yup I saw that...... > Suggestion: take the DBXMSSQLPlatform, overwrite #createDataTypesMap and fix > what you want. > Okay..... > Real solution we should do ? We should change DBXPlatform class >> > createDataTypesMap and map ALL types, and the overwrite > #createDataTypesMap in Firebird to trow erros (like it is now in > DBXPlatform class >> createDataTypesMap). > > Was that clear? I think so....... I'll start overriding createDataTypesMap. > Last comment, depending what you are doing, you may not need to transform > the values of a field and instead, get them as string. DBXRow >> #valueAt: > and valueXXX DO the conversion from string to the tpype. However, > #rawValueAt: and frinds, DO NOT. So, you can always use them and they will > always work, but getting the value as String. ok that's useful. At least I can get at the data in raw form. > I entered issue: > > http://code.google.com/p/dbxtalk/issues/detail?id=3 > > Thanks > > Mariano Many thanks for the detailed and useful response. > Date: Fri, 29 Apr 2011 06:00:20 -0300 > From: Diogenes Moreira <diogenes.moreira(a)gmail.com> > Subject: Re: [SqueakDBX] MSSQL, selecting nvarchar (other types too) > field causes DBXTypeNotSupported. > To: The complete and open-source solution to relational database > access <squeakdbx(a)lists.squeakfoundation.org> > Message-ID: <BANLkTi=MurApKvuzopN62TyBU2B10LSaRA(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi miguel.. > > why you dont use DBXMSSQLPlatform for MSSQL?? Because I was never able to open the connection to the database using DBXMSSQLPlatform. I started testing lower level libraries to check they were all working (freeTDS and OpenDBX). FreeTDS compile fine but then while I was trying to build OpenDBX the maintainer (Norbert I think...) suggested I use the ODBC driver instead. I tried it and it worked so I cut over to DBXOdbcPlatform. If you have any suggestions I'd love to go back to using the native driver. > > well, don't matter.. for give to you a right diagnosis, we need Odbc version > and what kind of driver.. (ADO or Direct) you are using . If you use ADO, > wich MDAC version..? I'll first try getting the raw values as suggested by Mariano. If I don't have luck with that then I chase this avenue. > > DBXTypeNotSupported is raising when the column type id returned by OpenDbx > isn´t in the types catalogates or is a "Real" unsupported type. > Mariano explains this in depth, thanks. > you can debug DBXPlatform class>> dataTypeAt: and see what is the id for > column type returned by OpenDBX.. and send it to us... will do..... > > together we will be find a bug and fix that. > Once again thanks for the prompt and useful responses. Miguel

3 7

DBXTalk (SqueakDBX) goes to Pharo 1.3
by Mariano Martinez Peck 29 Apr '11

29 Apr '11

Hi. This is just to let you know that SqueakDBX (soon DBXTalk) has 100% green tests in Pharo 1.3 without chaning one single line of code. In addition, half of the team is using Pharo 1.3 and the other one 1.2. We updated ConfigurationOfSquealDBX >> #stable Cheers -- Mariano http://marianopeck.wordpress.com

1 0

MSSQL, selecting nvarchar (other types too) field causes DBXTypeNotSupported.
by Miguel Sanchez 29 Apr '11

29 Apr '11

Hi all, I have a couple of problems but the second I'll pop in a second mail to have a clear subject line. I have a field on a table defined as nvarchar(50) that is throwing a DBXTypeNotSupported error despite the default supported type map on DBXPlatform which maps the datatype to a String. I've managed to avoid needing to select explicitly unsupported types (CLOB BLOC etc.....) My platform. Windows XP sp3 Pharo 1.1.1 one-click DBXOdbcPlatform Database (on localhost): MSSQL 2005 MSSQL Best Regards, Miguel

3 2

Re: Re: [SqueakDBX] Installing on Windows with MSSql backend was Re: [Esug-list] [ANN] ESUG supports
by Mikey.Sanchez＠gmail.com 11 Apr '11

11 Apr '11

1. If my application gains traction it will need a fairly serious object store. It also needs to integrate with 3rd party drelational databases. I need to make sure that if I opt for GemStone that I can "take" my relational DB connectivity with me. 2. I'll check the GLORP integration docs and the new loader. Thanks, Miguel On Apr 10, 2011 11:23pm, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > On Fri, Apr 8, 2011 at 4:01 PM, Miguel Sanchez mikey.sanchez(a)gmail.com> > wrote: > Hi, > OK after a few weeks hiatus I've managed to get all the SqueakDBX > tests to pass (ok two are still failing but they don't look like a big > deal. ) Yayyyyyyy! It helped using the right backend. I've all but > given up compiling openDBX. If I have time I'll go back to it for > completeness. I'll suggest some changes to the windows specific > documentation, or make them myself. How do you want to proceed? > Let me check with the rest of the team. > Soooooo now I have two questions that have occured to me. > 1. Is SqueakDBX ported to GemStone? (I'm guessing not).. > The problem is FFI. What do you want to do exacly ? I mean, why (for > what) you need SqueakDBX in Gemstone ? > 2. Is there a MsSQLPlatform on GLORP or does the SQLServerPlatform > integration work. (GLORP documentation makes reference to *rumours* of > SQLServer integration working.) Basically what is the state of the > GLORP/SqueakDBX rearchitecture work looking in order to use SueakDBX > backend? > Maybe you can take a look to: > http://www.squeakdbx.org/GLORP%20integration > However, the installation scripts are out-dated. We now use > ConfigurationOfGlorpDBX, not those loaders. > Best Regards, > Miguel > On 23 March 2011 23:41, Mariano Martinez Peck marianopeck(a)gmail.com> > wrote: > > > > > > On Wed, Mar 23, 2011 at 11:39 PM, Miguel Sanchez > mikey.sanchez(a)gmail.com> > > wrote: > >> > >> So it's a feature and not a bug.... ;-) > >> > > > > heheheheh > > > >> > >> I've got some stuff on compiling freeTDS and if I ever manage to > >> compile openDBX I'll put together a howto. > >> > > > > Ok. We can then integrate them where they should go: > > http://www.squeakdbx.org/Compiling%20for%20different%20backends > > > >> > >> On 23 March 2011 23:34, Mariano Martinez Peck marianopeck(a)gmail.com> > >> wrote: > >> > ehehehhehe Pharo > 1.1 is broken with this...this is a known bug > >> > (check > >> > Pharo issue tracker) > >> > But don't worry, just evaluate: DBXPlatform > >> > disableAutomaticConnectionReleaseOnGC and that's all. It is safe, > don't > >> > worry. > >> > > >> > BTW...if you have something to improve our documentation in the > website, > >> > please let us know. > >> > > >> > Cheers > >> > > >> > Mariano > >> > > >> > On Wed, Mar 23, 2011 at 11:29 PM, Miguel Sanchez > >> > mikey.sanchez(a)gmail.com> > >> > wrote: > >> >> > >> >> OK so after struggling to build openDBX (that one is ongoing), on > your > >> >> instruction I switched to using DBXOdbcPlatform and ......... > SUCCESS! > >> >> > >> >> Well ok partial success. I managed to open the connection and while > >> >> investigating the resultset of a select I started getting an error. > In > >> >> DBXConnection>>connect > >> >> On the line > >> >> self platform class isAutomaticConnectionReleaseOnGC ifTrue: [ > >> >> SqueakDBXSmalltalkDialect current > >> >> addObjectToGarbageCollect: self]. > >> >> /*during addObjectToGarbageCollect:*/ > >> >> I get the error: "Error: There is no free space in this set." > >> >> > >> >> Do I need to force a garbage collect? > >> >> > >> >> Best Regards, > >> >> > >> >> > >> >> Miguel > >> >> > >> >> > >> >> On 15 March 2011 18:22, Miguel Sanchez mikey.sanchez(a)gmail.com> > wrote: > >> >> > OK so I've had no luck getting to the bottom of the problem so > far. I > >> >> > still get thrown into "DBXRecovereableError: RECOVERABLE OpenDBX: > >> >> > Connecting to server failed" when calling DBXConnection>>open. > >> >> > > >> >> > I can connect with the Windows command-line tsql equivalent > >> >> > (sqlcmd.exe) so the DB user and permissions are correct. > >> >> > > >> >> > > >> >> > I said I was going to try and build from sources instead of the > >> >> > precompiled binaries. > >> >> self platform class isAutomaticConnectionReleaseOnGC ifTrue: [ > >> >> SqueakDBXSmalltalkDialect current > >> >> addObjectToGarbageCollect: self].> > >> >> I've downloaded and installed (finally) MinGW. I've (finally!) > >> >> > downloaded sources of opendbx 1.4.5 and freetds-0.8.2. > >> >> > > >> >> > freetds built fine and put the headers in an accessible place. but > >> >> > now > >> >> > when I try to configure opendbx I get the following: > >> >> > > >> >> > checking for style of include used by make... GNU > >> >> > checking for gcc... gcc > >> >> > checking whether the C compiler works... no > >> >> > configure: error: in `/opendbx-1.4.5': > >> >> > configure: error: C compiler cannot create executables > >> >> > See `config.log' for more details. > >> >> > > >> >> > config.log says the following: > >> >> > > >> >> > =============================================== > >> >> > > >> >> > configure:3972: gcc -qversion >&5 > >> >> > gcc.exe: unrecognized option '-qversion' > >> >> > gcc.exe: no input files > >> >> > configure:3983: $? = 1 > >> >> > configure:4003: checking whether the C compiler works > >> >> > configure:4025: gcc /local/include conftest.c >&5 > >> >> > > c:/mingw/bin/../lib/gcc/mingw32/4.5.2/../../../../mingw32/bin/ld.exe: > >> >> > cannot fin > >> >> > d C:/MinGW/msys/1.0/local/include: Permission denied^M > >> >> > collect2: ld returned 1 exit status^M > >> >> > configure:4029: $? = 1 > >> >> > configure:4067: result: no > >> >> > configure: failed program was: > >> >> > | /* confdefs.h */ > >> >> > > >> >> > ====================================== > >> >> > > >> >> > The directory C:/MinGW/msys/1.0/local/include exists and is > writable > >> >> > by > >> >> > me. > >> >> > > >> >> > Right now it feels like I'm trying to solve the problem of > building > >> >> > opendbx without knowing if it's getting me any closer to getting > >> >> > squeakDBX working. > >> >> > > >> >> > Any help would be appreciated. > >> >> > > >> >> > Miguel > >> >> > > >> > > >> > > > > > > -- > Mariano > http://marianopeck.wordpress.com

2 1

Installing on Windows with MSSql backend was Re: [Esug-list] [ANN] ESUG supports once again SqueakDBX
by Miguel Sanchez 10 Apr '11

10 Apr '11

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. 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. It's a little strange that the message occurs on "conn open" and not on "conn connect" (?). 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. Best Regards, Miguel On 4 March 2011 10:39, Mariano Martinez Peck <marianopeck(a)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(a)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(a)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(a)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. >> > >> > >

4 12

GlorpVarCharType >> typeString returns non working SQL
by Panu Suominen 06 Apr '11

06 Apr '11

There is little problem with varchar field type in Glorp. Following kind of table definitions in DescriptorSystem are not working: aTable createFieldNamed: 'zipcode' type: platform varChar. This is because GlorpVarCharType can return non working SQL. If one evaluates: (GlorpVarCharType new typeName: 'character varying') typeString it returns 'character varying(nil)' which does not compute (at least not with postgresql). This could be fixed by removing the typeString method from GlorpVarCharType (then GlorpAbstractStringType >> #typeString will be used which works ok). Currently I don't have opportunity to test this with other database systems. Other options could be setting some default for varchar length or removing DatabasePlatform >> #varChar and #varchar -methods. Any opinions? -- Panu

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

SqueakDBX April 2011