2009/10/13 Schwab,Wilhelm K <bschwab@anest.ufl.edu>
Hello all,
I had no idea I left such an inaccurate impression, but on re-reading what I wrote, it could be taken as though I sought to compete with Diego - sorry about that all around.
No no. I didn get that impressiont. I just asked because I wanted to know the differences :) Don't worry.
Let's try this again:
I found Diego's work lacking the ability to query table names and field names/types, wrote code to those things, and plan to make it available. Think of it as being an addition to Diego's package; the two can be merged.
One thing I do not like about Squeak/Pharo in general is the whacked up way it mixes
snapshots with startup and shutdown.
I don't understand this.
If I were to spin off of a new ODBC package, it would be to fix that.
The porting to which I referred is code that runs on top of OBBC, sockets, etc. That goes fairly well, and will spin off some collective benefits with time. As I said some time back, the best thing I can do to help with Pharo is to get myself hooked on it, at which point I will begin writing tools that would be of general interest.
It would help a lot to have a good way to export syntax colored code (HTML??) from MC packages.
I don't understand whot this is related with ODBC :(
My concern is that I might have comments that need to be removed for release. I live under a few non-disclosure agreements, and it would be bad to have a stray comment violate one of them. I am pretty careful about that now, but every so often find something that would have been more wisely placed outside of my code.
The worst news I have is that when I tried to move code into the October web image, the image refused to open an ODBC connection. In fact, the vm just crashed w/o writing diagnostic info to a file. I retreated to my current (July) image, and have been distracted with lots of progress on some complex fronts; however, I do need to get back to trying to identify the source of the crash.
yeah, I remember :(
Bill
------------------------------ *From:* pharo-project-bounces@lists.gforge.inria.fr [mailto: pharo-project-bounces@lists.gforge.inria.fr] *On Behalf Of *Mariano Martinez Peck *Sent:* Tuesday, October 13, 2009 10:02 AM *To:* Pharo-project@lists.gforge.inria.fr *Subject:* Re: [Pharo-project] ODBC
I would also like to know the difference (advantages and disadvatages) of Bill's driver and the one of Diego Gomez Deck which is:
http://wiki.squeak.org/squeak/2480 http://www.squeaksource.com/ODBC.html
Best,
Mariano
On Wed, Nov 11, 2009 at 11:38 PM, Carlos Crosetti <carlos@mostar.com.ar>wrote:
How is the ODBC port to Pharo going on?
-----Mensaje original----- De: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr]En nombre de Schwab,Wilhelm K Enviado el: Martes, 01 de Septiembre de 2009 05:15 p.m. Para: Pharo-project@lists.gforge.inria.fr Asunto: [Pharo-project] ODBCWarning
The porting continues... It is getting closer to doing something. It just raised an ODBCWarning about the server changing the language to us_english. Any ideas? Either I do not care or should set it up front??
One thing really surprised me, and note that I might have brought this on myself (though I think that is unlikely) by messing with startup and shutdown: the ODBCLibrary was stubbornly clinging to the Linux library from my home machine. I finally used
ODBCLibrary default initialize.
which seemed to put an end to the separation anxiety. Is there a better fix? I suppose I should try this in a clean image to see if there is really a problem therein, but that will be a little hard to do without a lot of my code, almost any of which either depends on changes I have made or could have caused the problem.
Maybe I should ask whether some of you use ODBC on Windows and Linux and have no problems moving between the machines.
Bill
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Internal Virus Database is out-of-date. Checked by AVG. Version: 7.5.560 / Virus Database: 269.21.6/1323 - Release Date: 10/03/2008 11:07 a.m.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project