SqueakDBX May 2011

squeakdbx@lists.squeakfoundation.org

9 participants
24 discussions

Should "GlorpSession>>register:" work?
by Panu Suominen 04 Jun '11

04 Jun '11

We have problem with reattaching objects to new session. Following code throws exception telling that connection is not open. |person| KLDatabase withSession: [:s| person := s readOneOf: KLPerson where: [:p| p id = 6127]. ]. KLDatabase withSession: [:s| s inUnitOfWorkDo: [ self halt. s register: person. Transcript show: person parameters. ] ]. The problem seems to be that "GlorpSession>>register:" does not check if there is an Glorp proxy inside the object being registered. Tutorial (http://www.eli.sdsu.edu/SmalltalkDocs/GlorpTutorial.pdf) states that it should reattach any nested objects (proxies) too but it does not. Is this known problem or am I doing something wrong? I can try to fix this if this is an actual bug. Of course using refresh: one can avoid this problem but it causes unnecessary database reads to occur. -- Panu

6 5

Re: [Seaside] Increasing the performances of a Seaside application
by Mariano Martinez Peck 29 May '11

29 May '11

On Sun, May 29, 2011 at 4:18 PM, stephane ducasse <stephane.ducasse(a)free.fr>wrote: > > > > > > It's a bit better. There's no starvation if the timeout is greater than > zero, but it's still a form of busy waiting, and it limits the number of > queries per second per connection to at most 1000 (actually 1000 / timeout). > To compare this with our native implementation - PostgresV3 - I measured 6k+ > queries per second per connection and it's still not optimized for Cog > (#perform: is slow on Cog). > > > > > > Thanks Levente. Unfortunatly I guess that's all we can do with a blocking > FFI :( > > Just that I understand why you do not have the same constraints that > levente? > What are they? because he does not have either a threaded ffi. > Because he uses a native client for PostgreSQL, that is, a driver implemented directly in Smalltalk: you open a socket and you implement the protocol the database specify. Easy. They use a Socket, and do not need FFI because the do not delegate to an external library. They implement the same as the external library but in Smalltalk. Why we don't do that? Because that ONLY and ONLY works for open-sources databases where they can make available the protocol specification so that you can build as many drivers as you want. However, non open-source databases (Oracle, SQLServer, Sybase, etc) DO NOT make the protocol available so you cannot just create your own driver. Instead, you have to use the driver THEY give you. Of course, for java they build drivers, so java guys do not depend on anybody, they just have they jdbc driver. SqueakDBX appeared to solve that problem. We, Smalltalk community, do not have that luck and we have to use one of the available drivers they do. All of the databases provide drivers written in C, and these are the easier to use from Smalltalk. Hence, we depend on an external library. The same happens with ODBC for example. Cheers > > Stef_______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > -- Mariano http://marianopeck.wordpress.com

1 0

Re: [Seaside] Increasing the performances of a Seaside application
by Mariano Martinez Peck 29 May '11

29 May '11

On Sun, May 29, 2011 at 2:19 PM, Levente Uzonyi <leves(a)elte.hu> wrote: > On Sun, 29 May 2011, Mariano Martinez Peck wrote: > > On Sun, May 29, 2011 at 4:06 AM, Levente Uzonyi <leves(a)elte.hu> wrote: >> >> On Sat, 28 May 2011, Mariano Martinez Peck wrote: >>> >>> >>> What are the errors that I must avoid making ? >>>>> >>>>>> >>>>>> >>>>> AFAIK SqueakDBX uses FFI which to my understanding means that it calls >>>>> block the entire VM. That reduces the amount of concurrency a single >>>>> image can handle. It also makes a connection pool more important. >>>>> >>>>> >>>>> Yes, FFI blocks the whole VM while a functions is being called. >>>>> However, >>>>> >>>> if >>>> and only if the database client library supports asynchronous queries, >>>> SqueakDBX will work asynchronously. Basically, we do a loop where we ask >>>> the >>>> backend if the query was ready. If it was not, we do a yield (we let >>>> other >>>> process of the image to run) and then continue the loop. >>>> >>>> >>> FYI: The expression "Processor yield" doesn't let all processes run, just >>> those which have the same priority. So using it in a loop starves all >>> lower >>> priority processes and results in busy waiting. >>> >>> >>> Thanks. I was not clear. What we actually do is: >> >> (code = OpenDBX resultTimeout) ifTrue: [ (Delay forMilliseconds: >> (aQuerySettings timeout asMiliseconds)) wait ]. >> >> Is that better? Even if it lets just run processes of the same priority, >> this is good anyway because what we want is at least be able to process >> other queries. Probably, those other processes are being done from other >> Process. >> > > It's a bit better. There's no starvation if the timeout is greater than > zero, but it's still a form of busy waiting, and it limits the number of > queries per second per connection to at most 1000 (actually 1000 / timeout). > To compare this with our native implementation - PostgresV3 - I measured 6k+ > queries per second per connection and it's still not optimized for Cog > (#perform: is slow on Cog). > > Thanks Levente. Unfortunatly I guess that's all we can do with a blocking FFI :( > > Levente > > > >> Thanks >> >> Mariano >> >> >> >> >>> Levente >>> >>> >>> >>> http://www.squeakdbx.org/documentation/Asynchronous%20queries >>>> >>>> Eliot implemented a multi-threaded FFI for Cog but so far I am not sure >>>> if >>>> it is already working. >>>> >>>> Cheers >>>> >>>> -- >>>> Mariano >>>> http://marianopeck.wordpress.com >>>> >>>> _______________________________________________ >>>> >>> seaside mailing list >>> seaside(a)lists.squeakfoundation.org >>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>> >>> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > -- Mariano http://marianopeck.wordpress.com

1 0

Re: [Seaside] Increasing the performances of a Seaside application
by Mariano Martinez Peck 29 May '11

29 May '11

On Sun, May 29, 2011 at 4:06 AM, Levente Uzonyi <leves(a)elte.hu> wrote: > On Sat, 28 May 2011, Mariano Martinez Peck wrote: > > >>> What are the errors that I must avoid making ? >>>> >>> >>> AFAIK SqueakDBX uses FFI which to my understanding means that it calls >>> block the entire VM. That reduces the amount of concurrency a single >>> image can handle. It also makes a connection pool more important. >>> >>> >>> Yes, FFI blocks the whole VM while a functions is being called. However, >> if >> and only if the database client library supports asynchronous queries, >> SqueakDBX will work asynchronously. Basically, we do a loop where we ask >> the >> backend if the query was ready. If it was not, we do a yield (we let other >> process of the image to run) and then continue the loop. >> > > FYI: The expression "Processor yield" doesn't let all processes run, just > those which have the same priority. So using it in a loop starves all lower > priority processes and results in busy waiting. > > Thanks. I was not clear. What we actually do is: (code = OpenDBX resultTimeout) ifTrue: [ (Delay forMilliseconds: (aQuerySettings timeout asMiliseconds)) wait ]. Is that better? Even if it lets just run processes of the same priority, this is good anyway because what we want is at least be able to process other queries. Probably, those other processes are being done from other Process. Thanks Mariano > > Levente > > > >> http://www.squeakdbx.org/documentation/Asynchronous%20queries >> >> Eliot implemented a multi-threaded FFI for Cog but so far I am not sure if >> it is already working. >> >> Cheers >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > -- Mariano http://marianopeck.wordpress.com

1 0

Re: [Seaside] Increasing the performances of a Seaside application
by Mariano Martinez Peck 29 May '11

29 May '11

On Sun, May 29, 2011 at 1:54 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > > On Sun, May 29, 2011 at 10:55 AM, Philippe Marschall < > philippe.marschall(a)gmail.com> wrote: > >> 2011/5/28 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> > >> >> >> >> > What are the errors that I must avoid making ? >> >> >> >> AFAIK SqueakDBX uses FFI which to my understanding means that it calls >> >> block the entire VM. That reduces the amount of concurrency a single >> >> image can handle. It also makes a connection pool more important. >> >> >> > >> > Yes, FFI blocks the whole VM while a functions is being called. However, >> if >> > and only if the database client library supports asynchronous queries, >> > SqueakDBX will work asynchronously. Basically, we do a loop where we ask >> the >> > backend if the query was ready. If it was not, we do a yield (we let >> other >> > process of the image to run) and then continue the loop. >> >> How do you avoid turning this into busy awaiting and still manage to >> get woken up when data is available? >> >> > What we do is > gmail shortcuts... What we do is: DBXBackend >> processNextResultSet: aConnection querySettings: aQuerySettings "Gets the next resultSet of the query. Depending on the type of query, it will return a DBXResult or DBXResultSet. If there is a timeout, it will cicle till this is finished." | returnCode | [self nextResultSet: aConnection querySettings: aQuerySettings onReturn: [:handle :code | returnCode := code. code = OpenDBX resultWithRows ifTrue: [ ^ self processResultWithRows: aConnection resultHandle: handle querySettings: aQuerySettings]. code = OpenDBX resultWithoutRows ifTrue: [ ^ self processResultWithoutRows: aConnection resultHandle: handle querySettings: aQuerySettings]. code = OpenDBX resultDone ifTrue: [^ nil]. (code = OpenDBX resultTimeout) ifTrue: [ (Delay forMilliseconds: (aQuerySettings timeout asMiliseconds)) wait ]. ]] doWhileTrue: [returnCode = OpenDBX resultTimeout]. OpenDBXDriverError signal: 'Uknown problem with executeStatement'. so....that is the ugly part of dbx... the method #nextResultSet:querySettings:onReturn: basically answers what the backend answers to: OpenDBX current apiQueryResult: aConnection handle handle: handleArray timeout: aQuerySettings timeoutAsDBXTimeSpec chunk: aQuerySettings pageSize. that answers what we call in the previous method "code". That "code" can mean "results wtih no row" for example when it was a DDL (a create table for example), a "result done" when we have finishes iterating all results , and "result timeout" that means that the query is not yet finished. In this case we have to always loop until we have one the two previous possibilities. Non of us is expert with processes and friends so we may be doing something wrong. If true, please let us know. Mariano > > >> Cheers >> Philippe >> _______________________________________________ >> seaside mailing list >> seaside(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> > > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com

1 0

Re: ideas for Smalltak GSoC 2011
by Mariano Martinez Peck 22 May '11

22 May '11

On Sun, May 22, 2011 at 5:01 PM, Carlos Crosetti < carlos.crosetti(a)mostar.com.ar> wrote: > Thans Mariano, I forgot SquakDBX had a solution. Regarding the native > client I mean a client that is fullt writen in Smaltalk code. Do uou know if > the Cincom VisialWorks EXDI cllient to Oracle is native too? > No, that should not be possible. Oracle is not open-source, so you don't know how to implement the library. Ok, I open a socket and then what? I don't know Cincom VisialWorks EXDI cllient to Oracle but I guess it talks by FFI or something like that to the Oracle C client library. Alan, can you tell us if it is like that? Otherwise, I don't understand ;) ----- Original Message ----- > *From:* Mariano Martinez Peck <marianopeck(a)gmail.com> > *To:* Carlos Crosetti <carlos.crosetti(a)mostar.com.ar> > *Cc:* esug.gsoc.adm2010(a)gmail.com > *Sent:* Sunday, May 22, 2011 9:35 AM > *Subject:* Re: ideas for Smalltak GSoC 2011 > > Carlos, you have SqueakDBX/GlorpDBX for exactly that. What you mean by "native Oracle client" > ? It is NOT possible to have a smalltalk driver for Oracle as there is for > PostgreSQL because Oracle is not open-source and you don't know the > protocol. So, you have to use the drivers they give you. > > Cheers > > > On Sun, May 22, 2011 at 1:35 AM, Carlos Crosetti < > carlos.crosetti(a)mostar.com.ar> wrote: > >> Hi, as Glorp benefits from having a native PostgreSQL client, as a >> Smalltalk developer I want to have a native Oracle client to seamlessly >> migrate back and froth from PortgreSQl to Oracle and in the opposite >> direction. >> >> Carlos Crosetti >> > > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com

1 2

Re: [opendbx] Mssql connection failed
by Mariano Martinez Peck 12 May '11

12 May '11

On Thu, May 12, 2011 at 1:21 PM, Alain rastoul <Alr.dev(a)free.fr> wrote: > Hi, > I finally got openDbx working with FreeTDS and ODBC, I don't know > what went wrong last night, I suppose my computer got tired ;) > This is great ! > > Well, these are great news!!! :) Please, if there is something we can improve in the documentation of the website, let us know. > However, I found > - a much better performance with ODBC backend (DBXOdbcPlatform) in > the test I did than with Freetds (DBXMSSQLPlatform) (run the test > below, changing DBXOdbcPlatform to DBXMSSQLPlatform). > With the ODBC backend the test ran about 2 times faster tha Did you see the benchmarks we have ? Check the classes DBXBigBenchmarks, DBXTinyBenchmarks and DBXMultipleForksBenchmarks. And this link: http://www.squeakdbx.org/Benchmarks > nt > MSSQL-freetds backend (needs explorations here) > - perhaps a problem with TinyInt datatype ? > (not very important) > Probably related to: http://www.squeakdbx.org/Mappings%20from%20String%20to%20specific%20squeak%… http://www.linuxnetworks.de/doc/index.php/OpenDBX/DBMS_Datatypes Cheers > The test below consist read the column definitions of syscolumns and > does not need any other database than master. > Set myhost, myport, mydb, myuser and mypassword as appropriate. > If you uncomment c.xprec, you will have the TinyInt error > > 500 timesRepeat: [ > | conn connectionSettings result sql | > > sql := 'select c.name, c.id, s.name , c.length --, c.xprec --, > c.xscale, c.xtype > from master..sysobjects as o > inner join master..syscolumns as c > on o.id = c.id > inner join master..systypes as s > on c.xtype = s.xtype > where o.name = ''syscolumns'''. > connectionSettings := DBXConnectionSettings > host: 'myhost' > port: '1884' > database: 'mydb' > userName: 'myuser' > userPassword: 'mypassword'. > [ conn := DBXConnection platform: DBXOdbcPlatform new > settings: > connectionSettings. > conn connect. > conn open. > result := conn execute: sql. > result rowsDo: [ :r | > 1 to: result columnCount do: [:c| > | v | > v := r rawValueAt: c.]]. > ] ensure: [ conn close ]]. > > Cheers, > Alain > > -- > Alain_rastoul > > > > ------------------------------------------------------------------------------ > Achieve unprecedented app performance and reliability > What every C/C++ and Fortran developer should know. > Learn how Intel has extended the reach of its next-generation tools > to help boost performance applications - inlcuding clusters. > http://p.sf.net/sfu/intel-dev2devmay > _______________________________________________ > libopendbx-devel mailing list > libopendbx-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/libopendbx-devel > http://www.linuxnetworks.de/doc/index.php/OpenDBX > -- Mariano http://marianopeck.wordpress.com

1 0

OpenDBX: Another command is already in progress
by John Toohey 11 May '11

11 May '11

I get this error a lot when my system is under load. According to the pgsql docs, I should do this, "PQgetResult must be called repeatedly until it returns a null pointer, *indicating* that the *command* *is* done." How do I handle this type of error in GlorpDBX? I'm using Pharo 1.2 and the Glorp/DBX build that was available when that was released. -- ~JT

3 12

Re: [Moose-dev] Re: Petit SQL Parser
by Mariano Martinez Peck 11 May '11

11 May '11

On Wed, May 11, 2011 at 4:06 PM, Fabrizio Perin <perin(a)iam.unibe.ch> wrote: > Hi Mariano, > well i did improve the parser itself adding also the alter table statement > and the select statement. I did also modify the architecture: now the parser > generate AST nodes instead the old "draft objects" abstraction. Anyway, as > far as i remember, no one attempt to implement any visualization on that. Do > you have something in your mind? > > Maybe. We don't know yet. We will analyze if having a (or part of) SQL parser will help us in something or not. This is related to this: http://forum.world.st/Call-for-ideas-for-DBXTalk-UI-td3513189.html So...I will have in mind your answer. Thanks Mariano > Cheers, > Fabrizio > > On 11 May 2011, at 01:01, Mariano Martinez Peck wrote: > > Hi Fabrizio. Any progress on this front ? > did someone do any kind of visualization once the parser was done? > > thanks > > mariano > > On Wed, Sep 1, 2010 at 3:46 PM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> >> >> On Wed, Sep 1, 2010 at 3:39 PM, Fabrizio Perin <perin(a)iam.unibe.ch>wrote: >> >>> Hi Marian, >>> here there is an example: >>> <Example.png> >>> >>> the one on the top is a class instead the one on the bottom is the >>> database table that the class access. >>> >>> This is a small example about what you can do by having information about >>> the code and the database in the same model. >>> >> >> Thanks Fabrizio. I got it. >> >> I think it would be cool to visualize the problem while maping inheritance >> chain and tables, and the different solutions: one table for each subclass, >> one big table with NULLable fields and a type field, etc..... >> >> >> >> >> >>> >>> Cheers, >>> >>> Fabrizio >>> >>> On 1 Sep 2010, at 14:18, Mariano Martinez Peck wrote: >>> >>> >>> >>> On Tue, Aug 31, 2010 at 7:36 AM, Tudor Girba <tudor.girba(a)gmail.com>wrote: >>> >>>> It is useful when you want to understand a database and possibly it's >>>> relationship with code. >>>> >>>> For example, an SQL query in the string of some Java code that refers to >>>> a certain table creates a logical dependency. If we can relate the two >>>> worlds, we can build larger analyses. >>>> >>>> Does it make better sense now? >>>> >>>> >>> Yes. I think that yes :) >>> >>> I was thinking more from a database driver point of view, not from >>> visualization. Sorry, I forgot this was moose hahhaha >>> >>> >>> >>>> Doru >>>> >>>> >>>> >>>> On 31 Aug 2010, at 07:16, Mariano Martinez Peck wrote: >>>> >>>> Sorry for my completely ignorance, but what can be the use of parsing >>>>> SQL? >>>>> >>>>> Suppose from the point of view of a database driver that receives >>>>> queries, or from a ORM point of view....does it make sense for something? >>>>> >>>>> Thanks >>>>> >>>>> Mariano >>>>> >>>>> On Tue, Aug 31, 2010 at 12:59 AM, Tudor Girba <tudor.girba(a)gmail.com> >>>>> wrote: >>>>> That is cool news. I will take a look in the following days. >>>>> >>>>> Cheers, >>>>> Doru >>>>> >>>>> >>>>> >>>>> On 30 Aug 2010, at 16:00, Fabrizio Perin wrote: >>>>> >>>>> Hi all, >>>>> i did implement an SQL parser using Petit Parser. I toke the grammar >>>>> specification from SQLite http://www.sqlite.org/lang.html . The >>>>> grammar implemented is not complete, for now i did implement "just" the >>>>> create table statement, it means that you should be able to parse at least a >>>>> script for create the database. >>>>> >>>>> The code is in squeaksource >>>>> http://www.squeaksource.com/@09zbthA-fDDfyUNQ/_OIex3aA . >>>>> >>>>> To download it you can evaluate this: >>>>> >>>>> Gofer new >>>>> squeaksource: 'PetitSQLParser'; >>>>> package: 'ConfigurationOfPetitSQLParser'; >>>>> load. >>>>> (Smalltalk at: #ConfigurationOfPetitSQLParser) perform: #loadDefault >>>>> in the repository there are several packages: the core contains the >>>>> parser for the grammar. >>>>> >>>>> In the package parser there is a parser that instantiate some draft >>>>> objects representing relational elements. >>>>> >>>>> In the next future i will start to implement also other statements. >>>>> >>>>> If you start to use it and you have some problem please let me know. >>>>> >>>>> Cheers, >>>>> >>>>> Fabrizio >>>>> >>>>> _______________________________________________ >>>>> Moose-dev mailing list >>>>> Moose-dev(a)iam.unibe.ch >>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>>> >>>>> -- >>>>> www.tudorgirba.com >>>>> >>>>> "No matter how many recipes we know, we still value a chef." >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Moose-dev mailing list >>>>> Moose-dev(a)iam.unibe.ch >>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>>> >>>>> _______________________________________________ >>>>> Moose-dev mailing list >>>>> Moose-dev(a)iam.unibe.ch >>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>>> >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "What is more important: To be happy, or to make happy?" >>>> >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> Moose-dev(a)iam.unibe.ch >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> >> > > > -- > Mariano > http://marianopeck.wordpress.com > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- Mariano http://marianopeck.wordpress.com

1 0

Call for ideas for DBXTalk UI
by Mariano Martinez Peck 11 May '11

11 May '11

Hi guys. Thanks to the ESUG SummerTalk, DBXTalk team has started to work with the new products of the DBXTalk suite. However, for one of the tools in special we would like to hear your opinion. Just a little introduction to the two other tools: 1) A new Glorp port from VW to Pharo. In addition, we provide the DBX driver for Glorp, by the name of GlorpDBX. Guillermo Polito is mostly working on this. 2) A new tool that uses Magritte and the database metadata to automatically generate the mappings between objects and tables. The idea is to do it two-way: a) read the metadata from an existing database -> create magritte descriptions -> generate Glorp mappings -> query with Glorp b) write magritte descriptions for the mappings -> generate database schema -> generate Glorp mappings -> query with Glorp or something like that....it is not completely decided but that's the idea. This way we can autogenerate the Glorp mappings and then use Glorp normally. Santiago Bragagnolo is working mostly on this. The third product, and here the question, is going to be a UI for the DBXTalk suite. This UI would do the core functionalities of tools like SQLDeveloper, MySQL Explorer, pgAdmin, etc. This is basically: - visualize and get information of: tables, views, schemas, relations, indexes, etc. - be able to modify the previous items and impact them in the database - write queries and get results So...why this tool if we can also use external tools like SQLDeveloper, MySQL Explorer, pgAdmin, etc ? a couple of reasons: 1) having the tool inside the image is easier (just the same way you sometimes install an Eclipse plugin instead of using such programs) 2) the same tool works for all databases 3) we can customize it with particular things of DBX Gisela Decuzzi is working mostly on this. Now....what use cases do you think are useful for such UI ? what kind of things would you like ? what things we can do that are related to Glorp and to the magritte tool? what things can we do to have even more advantages than just using external programs ? I have the following things in mind: - Special console for DBX/Glorp logs. - Be able to edit Magritte description for mappings. - Sync the tables and mapping while edditing. - A new inspector for inspecting restultsets, where you see one rows and columns. Let us know. Once again, thanks ESUG for the sponsorship to the team. Mariano http://marianopeck.wordpress.com

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

SqueakDBX May 2011