[Pharo-project] ODBC, loadFFI and friends!
Please have a look at
http://www.squeaksource.com/PharoInbox/DolphinCompatibility-ODBC-BillSchwab....
It adds a few methods that I missed (one could argue that I should package >some of this separately) and gives access to table and field names.
Hi Bill, I once contacted Frank Urbach (creator of the package on squeaksource), but got no response. However: http://www.squeaksource.com/ODBC is "Read And Write" so you can integrate your changes easily. It's MIT and open anyway so anything that makes life easier should be added. Thanks Torsten -- GMX DSL Doppel-Flat ab 19,99 €/mtl.! Jetzt auch mit gratis Notebook-Flat! http://portal.gmx.net/de/go/dsl
On Dec 9, 2010, at 7:54 PM, Torsten Bergmann wrote:
Please have a look at
http://www.squeaksource.com/PharoInbox/DolphinCompatibility-ODBC-BillSchwab....
It adds a few methods that I missed (one could argue that I should package >some of this separately) and gives access to table and field names.
Hi Bill,
I once contacted Frank Urbach (creator of the package on squeaksource), but got no response.
but he replied to me and I forwarded to you. You never got it?
However: http://www.squeaksource.com/ODBC is "Read And Write" so you can integrate your changes easily. It's MIT and open anyway so anything that makes life easier should be added.
Torsten, I can just shove it out there, but I would feel better if someone else would try it and report on success/failure or good/bad opinions of it. Beyond that, the question is whether anyone cares about enumerating tables and fields? If there is interest, it is worth talking about what might be better kept on my side. Some of the questionable methods are "redundant spellings" that are of interest to me because I have a lot of senders. What do you think? Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Torsten Bergmann [astares@gmx.de] Sent: Thursday, December 09, 2010 1:54 PM To: pharo-project@lists.gforge.inria.fr Subject: [Pharo-project] ODBC, loadFFI and friends!
Please have a look at
http://www.squeaksource.com/PharoInbox/DolphinCompatibility-ODBC-BillSchwab....
It adds a few methods that I missed (one could argue that I should package >some of this separately) and gives access to table and field names.
Hi Bill, I once contacted Frank Urbach (creator of the package on squeaksource), but got no response. However: http://www.squeaksource.com/ODBC is "Read And Write" so you can integrate your changes easily. It's MIT and open anyway so anything that makes life easier should be added. Thanks Torsten -- GMX DSL Doppel-Flat ab 19,99 €/mtl.! Jetzt auch mit gratis Notebook-Flat! http://portal.gmx.net/de/go/dsl
Is there any way to initialize a TestCase subclass *once* and set up all the necessary stuff I need for all test cases in that subclass ? Let's say I want to test some socket stuff and connect only ONCE (and reuse that socket over and over, leaving it open), how should I proceed? I don't want to open and close the socket with #setUp and #tearDown each and every time so a one-time initialization for the class (and a proper cleanup ) everytime I run the test suite is what I am looking for. Suggestions? Is there any Sunit version/fork/extension that would allow me to do that? Did I miss something obvious and I have exactly what I need in front on me in my class browser right now or we can't do this with what's there now? If it's not there, does anyone think it would be worth we add such a feature ? I volunteer to get it done! tia! ----------------- Benoit St-Jean Yahoo! Messenger: bstjean A standpoint is an intellectual horizon of radius zero. (Albert Einstein)
TestResource is what you look for. Lukas On 12 January 2011 19:13, Benoit St-Jean <bstjean@yahoo.com> wrote:
Is there any way to initialize a TestCase subclass *once* and set up all the necessary stuff I need for all test cases in that subclass ?
Let's say I want to test some socket stuff and connect only ONCE (and reuse that socket over and over, leaving it open), how should I proceed? I don't want to open and close the socket with #setUp and #tearDown each and every time so a one-time initialization for the class (and a proper cleanup ) everytime I run the test suite is what I am looking for. Suggestions? Is there any Sunit version/fork/extension that would allow me to do that?
Did I miss something obvious and I have exactly what I need in front on me in my class browser right now or we can't do this with what's there now?
If it's not there, does anyone think it would be worth we add such a feature ? I volunteer to get it done!
tia!
----------------- Benoit St-Jean Yahoo! Messenger: bstjean A standpoint is an intellectual horizon of radius zero. (Albert Einstein)
-- Lukas Renggli www.lukas-renggli.ch
On Wed, Jan 12, 2011 at 7:13 PM, Benoit St-Jean <bstjean@yahoo.com> wrote:
Is there any way to initialize a TestCase subclass *once* and set up all the necessary stuff I need for all test cases in that subclass ?
Let's say I want to test some socket stuff and connect only ONCE (and reuse that socket over and over, leaving it open), how should I proceed? I don't want to open and close the socket with #setUp and #tearDown each and every time so a one-time initialization for the class (and a proper cleanup ) everytime I run the test suite is what I am looking for. Suggestions? Is there any Sunit version/fork/extension that would allow me to do that?
As Lukas said, the best solution here is using TestResource. I did exaclty what you describe there for the SqueakDBX tests and the connections to the database.
Did I miss something obvious and I have exactly what I need in front on me in my class browser right now or we can't do this with what's there now?
If it's not there, does anyone think it would be worth we add such a feature ? I volunteer to get it done!
tia!
----------------- Benoit St-Jean Yahoo! Messenger: bstjean A standpoint is an intellectual horizon of radius zero. (Albert Einstein)
participants (6)
-
Benoit St-Jean -
Lukas Renggli -
Mariano Martinez Peck -
Schwab,Wilhelm K -
Stéphane Ducasse -
Torsten Bergmann