Hello all,
I think I have the catalog (tables and
field name/type given a table name) working. The latest ODBC offering
appears to work, but in fairness to me, it does not work the same way it did
(some time ago) when I crossed database access off of my
potential-show-stopper list.
Re the warnings about change of language,
for some strange reason, I find it very easy to believe that this is a
Microsoft idiosyncrasy and so I added a suitable #on:do: to capture the
warning. That could be bad though; better ideas are welcome.
The
problem I had going from Linux to Windows will probably persist. Of
course, I would like to see the startup/shutdown system revised to make such
things easier to get right, after which it would hopefully become short work
to fix.
The ODBC package derives ODBCRow from IdentityDictionary and
ODBCResultSet from Stream. IMHO, it always seems cleaner to compose
rather than inherit the limited functionality that the base class
provides. However, the inheritance is not really hurting anything here;
socket addresses being inherited from byte arrays *is* hurting us. I
brushed up against that at one point, but was able to work around it.
When it gets between me and something I need, I will introduce an
InternetAddress class and try to lazily resolve names and addresses, fix the
printing, etc.
Bill
-----Original
Message-----
From:
pharo-project-bounces@lists.gforge.inria.fr [mailto:
pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of
Schwab,Wilhelm K
Sent: Tuesday, September 01, 2009 3:15 PM
To:
Pharo-project@lists.gforge.inria.frSubject:
[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.frhttp://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project_______________________________________________
Pharo-project
mailing list
Pharo-project@lists.gforge.inria.frhttp://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project