From Tod Olson Mon Feb 2 15:28:02 1998 From: Tod Olson (Tod Olson) Date: Mon, 02 Feb 1998 09:28:02 -0600 Subject: [DB-SIG] Database API clarifications In-Reply-To: Your message of "Sat, 31 Jan 1998 11:01:46 +0100" References: <34D2F68A.50582178@uni-duesseldorf.de> Message-ID: <199802021528.JAA12846@stone.lib.uchicago.edu> >>>>> "M" == M -A Lemburg writes: M> Bill Tutt wrote: >> >> > me: >> > Is that ok ? I'll add it to my API 1.1. draft then. >> > >> Well, close, but preferably return None instead of 0, this is Python after >> all. :) M> Right -- has a better sound to it :-) That being the case, how about cursor.nextset() returns self. Two benefits: - Allows cursor.nextset().fetchall(), which is nice for interactive typing. - Works nicely if the database-API evolves to treat result sets as objects. Next question: should a programmer be able to do cursor.execute(big_query) while cursor.nextset(): cursor.fetchall() to process all the rows of all the results, or must the programmer do cursor.execute(big_query) cursor.fetchall() while cursor.nextset(): cursor.fetchall() I personally prefer the former, since cursor.fetchall will usually be some larger block of code and need to be duplicated. Other opinions? Tod A. Olson "How do you know I'm mad?" said Alice. ta-olson@uchicago.edu "If you weren't mad, you wouldn't have The University of Chicago Library come here," said the Cat. _______________ DB-SIG - SIG on Tabular Databases in Python send messages to: db-sig@python.org administrivia to: db-sig-request@python.org _______________ From lemburg@uni-duesseldorf.de Mon Feb 2 18:21:44 1998 From: lemburg@uni-duesseldorf.de (M.-A. Lemburg) Date: Mon, 02 Feb 1998 19:21:44 +0100 Subject: [DB-SIG] Database API clarifications References: <34D2F68A.50582178@uni-duesseldorf.de> <199802021528.JAA12846@stone.lib.uchicago.edu> Message-ID: <34D60EB8.19552B87@uni-duesseldorf.de> Tod Olson wrote: > > [adding cursor.nextset()] > > How about cursor.nextset() returns self. Two > benefits: > > - Allows cursor.nextset().fetchall(), which is nice for interactive > typing. > > - Works nicely if the database-API evolves to treat result sets as > objects. That's a religous topic :-) just like many people would like to see list.sort() return list and not None. We could specify it to return a truth value (None is false, 1 and self are true). That leaves enough space for future extensions. Objections ? > Next question: should a programmer be able to do > > cursor.execute(big_query) > while cursor.nextset(): > cursor.fetchall() > > to process all the rows of all the results, or must the programmer do > > cursor.execute(big_query) > cursor.fetchall() > while cursor.nextset(): > cursor.fetchall() cursor.nextset() will have to switch to the next result set in any case, so the latter is more appropriate. You can write it like this: cursor.execute(big_query) while 1: cursor.fetchall() if not cursor.nextset(): break without having to copy anything (Python's idiom for do {...} while (...)). -- Marc-Andre Lemburg _______________ DB-SIG - SIG on Tabular Databases in Python send messages to: db-sig@python.org administrivia to: db-sig-request@python.org _______________ From Tod Olson Mon Feb 2 23:34:02 1998 From: Tod Olson (Tod Olson) Date: Mon, 02 Feb 1998 17:34:02 -0600 Subject: [DB-SIG] Database API clarifications In-Reply-To: Your message of "Mon, 02 Feb 1998 19:21:44 +0100" References: <34D60EB8.19552B87@uni-duesseldorf.de> Message-ID: <199802022334.RAA04727@stone.lib.uchicago.edu> >>>>> "M" == M -A Lemburg writes: M> Tod Olson wrote: >> >> [adding cursor.nextset()] >> >> How about cursor.nextset() returns self. Two >> benefits: >> >> - Allows cursor.nextset().fetchall(), which is nice for interactive >> typing. >> >> - Works nicely if the database-API evolves to treat result sets as >> objects. M> That's a religous topic :-) just like many people would like to see M> list.sort() return list and not None. We could specify it to return M> a truth value (None is false, 1 and self are true). That leaves M> enough space for future extensions. Objections ? So much for slipping that in under the radar. ;) More to the point, I was thinking of self because it's not just a truth value, it is a value that the programmer can use immediately. Anyhow, an unspecified truth value seems reasonable. M> cursor.nextset() will have to switch to the next result set in any M> case, so the latter is more appropriate. You can write it like this: M> cursor.execute(big_query) M> while 1: M> cursor.fetchall() M> if not cursor.nextset(): M> break M> without having to copy anything (Python's idiom for do {...} while M> (...)). Hmm, that does remove some of the advantage to cursor.nextset() returning self. But it is the idiom. WRT cursor.nextset() switching to the next result set: in Sybase, at least, this only happens after all of the rows from the current result set have been fetched. More precisely, I have found no way to cancel the remainder of the current result set and start up with the next, I have to cancel the whole command. This being the case, for Sybase it may be appropriate to raise an exception if the programmer attempts to skip to the next result set before processing all the rows of the current one. If you disagree, perhaps the database-API (c|sh)ould leave this particular behavior undefined until the db-sig has more experience with multiple result sets. Tod A. Olson "How do you know I'm mad?" said Alice. ta-olson@uchicago.edu "If you weren't mad, you wouldn't have The University of Chicago Library come here," said the Cat. _______________ DB-SIG - SIG on Tabular Databases in Python send messages to: db-sig@python.org administrivia to: db-sig-request@python.org _______________ From aaron@cs.rutgers.edu Wed Feb 11 23:28:45 1998 From: aaron@cs.rutgers.edu (Aaron Watters) Date: Wed, 11 Feb 1998 18:28:45 -0500 Subject: [DB-SIG] Re: Python and Oracle Message-ID: <199802121128.GAA16659@aramis.rutgers.edu> Hi: I thought I'd pass this to the db-sig in case any of you db folks missed it on the big list. I'm having a similar problem with /product/8.0.3/lib but my mystery symbol is skgupec. Please help us aarons! -- Aaron Watters === Subject: Re: Python and Oracle From: aaron@infinity.com Date: 1998/02/10 Message-ID: <887076525.608567297@dejanews.com> Newsgroups: comp.lang.python [More Headers] Hi -- We ran into the same error as you did (unable to allocate memory on user side) when trying to use the python oracledb module with an oracle8 server. We tried re-building the python oracledb module against the new set of oracle8 libraries and header files, and we then re-ran our test case. Unfortunately, *this* time around, we weren't even able to import the oracledb module! We got a symbol relocation error -- the Oracle8 sharedLib libclntsh.so.1.0 was looking for the symbol "slpmprodstab". We couldn't seem to find this symbol anywhere! 2 questions: have you made any progress since December using Oracle8 with Python. In particular, have you solved the "memory allocation" error you were seeing? And have you run into the run-time linking error that we're seeing? We would appreciate greatly any insight you have on this! Thanks! Aaron Hallmark _______________ DB-SIG - SIG on Tabular Databases in Python send messages to: db-sig@python.org administrivia to: db-sig-request@python.org _______________ From pa@tekla.fi Thu Feb 12 12:45:04 1998 From: pa@tekla.fi (Harri Pasanen) Date: Thu, 12 Feb 1998 14:45:04 +0200 Subject: [DB-SIG] Win32 ODBC module source Message-ID: <199802121246.OAA17718@marathon.tekla.fi> Where can I find the Win32 ODBC module source, and does it require other support than standard Python 1.5 source archive to compile? Harri Pasanen - home page http://www.iki.fi/hpa/ _______________ DB-SIG - SIG on Tabular Databases in Python send messages to: db-sig@python.org administrivia to: db-sig-request@python.org _______________ From bac@ivc.com Thu Feb 12 14:08:46 1998 From: bac@ivc.com (Brad Crittenden) Date: Thu, 12 Feb 1998 09:08:46 -0500 Subject: [DB-SIG] client requirements for informix module Message-ID: <199802121409.JAA17207@ivc1.ivc.com> hi: this is not a python-specific question but i hope someone can give me a hand. i've used the oracledb module with great success in the past. now i have to access a remote informix database. both client and informix servers are solaris. what client-side software needs to be installed to use the informix module? i assume it is their equivalent of oracle's sqlnet. what is it called? having never dealt with informix before i'm at a bit of a loss. to make matters worse i must communicate the requirements via a non-technical project manager to have the installation work done by a quasi-hostile sysadmin. thus, i need to be as precise and specific as possible. any help is greatly appreciated. thanks, brad _______________ DB-SIG - SIG on Tabular Databases in Python send messages to: db-sig@python.org administrivia to: db-sig-request@python.org _______________ From aaron@cs.rutgers.edu Thu Feb 12 03:35:12 1998 From: aaron@cs.rutgers.edu (Aaron Watters) Date: Wed, 11 Feb 1998 22:35:12 -0500 Subject: [DB-SIG] RE: Python 1.5 and Oracle 8 Message-ID: <199802121535.KAA21328@aramis.rutgers.edu> Well, I just got it to work with ora/solaris 8.0.3, py 1.5 The pertinent part of the makefile below. Slice it into the middle of the excellent digicool makefile. -- aaron watters ps: sheesh, you mean i have to do everything myself? ;c) > libdump= -lm $(OLIB)/libicd.a $(OLIB)/libserver.a $(OLIB)/nigcon.o $(OLIB)/__fstd.o $(OLIB)/libicx.a $(OLIB)/libslax.a $(OLIB)/nigtab.o $(OLIB)/libagent.a $(OLIB)/libmm.a $(OLIB)/libslpm.a $(OLIB)/nnfgt.o $(OLIB)/libclient.a $(OLIB)/libncr.a $(OLIB)/libsql.a $(OLIB)/ntcontab.o $(OLIB)/libndw1.a $(OLIB)/libsqlplus.a $(OLIB)/osntabst.o $(OLIB)/libnetv2.a $(OLIB)/libsvrmgrl.a $(OLIB)/s0main.o $(OLIB)/libcommon.a $(OLIB)/libnetwork.a $(OLIB)/scorept.o $(OLIB)/libcore4.a $(OLIB)/libnlsrtl3.a $(OLIB)/naect.o $(OLIB)/smalmain.o $(OLIB)/libepc.a $(OLIB)/libnttcp.a $(OLIB)/naedhs.o $(OLIB)/sscoreed.o $(OLIB)/libepcfe.a $(OLIB)/libplsb.a $(OLIB)/naeet.o $(OLIB)/libepcpt.a $(OLIB)/libplsf.a $(OLIB)/libextp.a $(OLIB)/libpsa.a $(OLIB)/nautab.o $(OLIB)/libgeneric.a $(OLIB)/libpsd.a $(OLIB)/ncrstab.o > > libdumpedit= -lm $(OLIB)/libicd.a $(OLIB)/libserver.a $(OLIB)/nigcon.o $(OLIB)/__fstd.o $(OLIB)/libicx.a $(OLIB)/libslax.a $(OLIB)/libagent.a $(OLIB)/libmm.a $(OLIB)/libslpm.a $(OLIB)/nnfgt.o $(OLIB)/libncr.a $(OLIB)/libsql.a $(OLIB)/ntcontab.o $(OLIB)/libndw1.a $(OLIB)/libsqlplus.a $(OLIB)/libnetv2.a $(OLIB)/libsvrmgrl.a $(OLIB)/libcommon.a $(OLIB)/scorept.o $(OLIB)/libcore4.a $(OLIB)/libnlsrtl3.a $(OLIB)/naect.o $(OLIB)/libepc.a $(OLIB)/libnttcp.a $(OLIB)/naedhs.o $(OLIB)/sscoreed.o $(OLIB)/libplsb.a $(OLIB)/naeet.o $(OLIB)/libepcpt.a $(OLIB)/libextp.a $(OLIB)/libpsa.a $(OLIB)/libpsd.a > > # bad symbol in ncrstab.o, removed (kjcroctx) > > # ['libclntsh.so.1.0', 'libclntsh.so', 'libplsf.a', 'libclient.a', 'libgeneric.a'] > # all contain skguout: removed. > > # ['libclntsh.so.1.0', 'libclntsh.so', 'libnetwork.a', 'libclient.a', 'libepcfe.a'] > # all contain orol: removed > > # conflicts : > # nigtab.o osntabst.o > # s0main.o smalmain.o > # libnetwork.a nautab.o > # libnetwork.a osntabst.o > # libnetwork.a nigtab.o > # compatible > # libnetork.a s0main.o > # all deleted from libdumpedit > # the following are the chosen ones > #addback= $(OLIB)/libnetwork.a $(OLIB)/s0main.o > addback= $(OLIB)/libclient.a $(OLIB)/libclntsh.so > > # Your Libraries > YOURLIBS=$(libdumpedit) $(addback) > > # just keep trying to resolve the names, generates warnings... > EXTRALD=$(YOURLIBS) $(YOURLIBS) _______________ DB-SIG - SIG on Tabular Databases in Python send messages to: db-sig@python.org administrivia to: db-sig-request@python.org _______________ From cjr@euronet.nl Thu Feb 12 16:08:50 1998 From: cjr@euronet.nl (cjr@euronet.nl) Date: Thu, 12 Feb 1998 16:08:50 +0000 (WET) Subject: [DB-SIG] Re: Python and Oracle In-Reply-To: <199802121128.GAA16659@aramis.rutgers.edu> from "Aaron Watters" at Feb 11, 98 06:28:45 pm Message-ID: <199802121608.QAA17025@axiom.euronet.nl> My two cents, not with Oracle8 but seemingly related with Oracle7: Using the libclntsh.so.1.0 that I have around for Oracle7.3.2.2 I can do: Python 1.5 (#8, Jan 19 1998, 19:46:22) [GCC 2.7.2.2] on sunos5 Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam >>> import oracledb >>> conn = oracledb.oracledb('siteboost/mypasswd@develop') >>> i But when prefixing this with http headers and running it as a CGI script, I receive the dreaded ORA-01019-unable-to-allocate-memory-on- the-user-side error. A search in the database newsgroups for the phenomenon indicated that the error is presumed to result from mixing library versions. Well, I did some weird permutations of the available stuff in the Makefile, running into ever different missing symbols. On the other hand, it seems that my problem is caused by some ulimit imposed by apache on CGI scripts. I'm clueless and just about ready to talk my boss into shedding this oracle thing and stepping over to gadfly ;-). cjr > > > > Hi: I thought I'd pass this to the db-sig in case any of you db folks > missed it on the big list. > > I'm having a similar problem with /product/8.0.3/lib but my mystery > symbol is skgupec. Please help us aarons! -- Aaron Watters > > === > Subject: Re: Python and Oracle > From: aaron@infinity.com > Date: 1998/02/10 > Message-ID: <887076525.608567297@dejanews.com> > Newsgroups: comp.lang.python > [More Headers] > > > Hi -- > > We ran into the same error as you did (unable to allocate memory on user > side) when trying to use the python oracledb module with an oracle8 > server. > > We tried re-building the python oracledb module against the new set of > oracle8 libraries and header files, and we then re-ran our test case. > > Unfortunately, *this* time around, we weren't even able to import the > oracledb module! We got a symbol relocation error -- the Oracle8 > sharedLib libclntsh.so.1.0 was looking for the symbol "slpmprodstab". We > couldn't seem to find this symbol anywhere! > > 2 questions: have you made any progress since December using Oracle8 with > Python. In particular, have you solved the "memory allocation" error you > were seeing? And have you run into the run-time linking error that we're > seeing? We would appreciate greatly any insight you have on this! > > Thanks! > > Aaron Hallmark > > > _______________ > DB-SIG - SIG on Tabular Databases in Python > > send messages to: db-sig@python.org > administrivia to: db-sig-request@python.org > _______________ > _______________ DB-SIG - SIG on Tabular Databases in Python send messages to: db-sig@python.org administrivia to: db-sig-request@python.org _______________ From aaron@cs.rutgers.edu Thu Feb 19 13:44:17 1998 From: aaron@cs.rutgers.edu (Aaron Watters) Date: Thu, 19 Feb 1998 08:44:17 -0500 Subject: [DB-SIG] sybase? Message-ID: <34EC3731.33E2@cs.rutgers.edu> Thought I'd check. The latest Sybase module is the non-dbapi compliant sybase module in ftp.python.org/pub/python/contrib/Databases right? Wasn't someone working on a new one? I hope I'm wrong. thanks, -- Aaron Watters _______________ DB-SIG - SIG on Tabular Databases in Python send messages to: db-sig@python.org administrivia to: db-sig-request@python.org _______________ From jim.fulton@digicool.com Thu Feb 19 14:54:57 1998 From: jim.fulton@digicool.com (Jim Fulton) Date: Thu, 19 Feb 1998 09:54:57 -0500 Subject: [DB-SIG] sybase? References: <34EC3731.33E2@cs.rutgers.edu> Message-ID: <34EC47C1.553E@digicool.com> Aaron Watters wrote: > > Thought I'd check. The latest > Sybase module is the non-dbapi > compliant sybase module in > ftp.python.org/pub/python/contrib/Databases > right? Wasn't someone working on a new > one? There is a DBI-complientish module at: http://starship.skyport.net/~pgodman/ Jim -- Jim Fulton mailto:jim@digicool.com Technical Director (888) 344-4332 Python Powered! Digital Creations http://www.digicool.com http://www.python.org _______________ DB-SIG - SIG on Tabular Databases in Python send messages to: db-sig@python.org administrivia to: db-sig-request@python.org _______________ From Tod Olson Thu Feb 19 15:07:19 1998 From: Tod Olson (Tod Olson) Date: Thu, 19 Feb 1998 09:07:19 -0600 Subject: [DB-SIG] sybase? In-Reply-To: Your message of "Thu, 19 Feb 1998 08:44:17 -0500" References: <34EC3731.33E2@cs.rutgers.edu> Message-ID: <199802191507.JAA06881@stone.lib.uchicago.edu> >>>>> "AW" == Aaron Watters writes: AW> Thought I'd check. The latest Sybase module is the non-dbapi AW> compliant sybase module in AW> ftp.python.org/pub/python/contrib/Databases right? Wasn't someone AW> working on a new one? I'm working on one based on ct-lib. I need to allocate a few more days to work on it before I'm ready to release an early version. Peter Godman is also working on one. AW> I hope I'm wrong. In what sense? If you're limited to ct-lib and have fairly straightforward needs, I may be able to expidite my work. Tod A. Olson "How do you know I'm mad?" said Alice. ta-olson@uchicago.edu "If you weren't mad, you wouldn't have The University of Chicago Library come here," said the Cat. _______________ DB-SIG - SIG on Tabular Databases in Python send messages to: db-sig@python.org administrivia to: db-sig-request@python.org _______________ From raf@comdyn.com.au Fri Feb 20 05:30:56 1998 From: raf@comdyn.com.au (raf) Date: Fri, 20 Feb 1998 16:30:56 +1100 Subject: [DB-SIG] sybase? Message-ID: <199802200530.QAA04271@mali.comdyn.com.au> >Thought I'd check. The latest >Sybase module is the non-dbapi >compliant sybase module in >ftp.python.org/pub/python/contrib/Databases >right? Wasn't someone working on a new >one? >I hope I'm wrong. there's a much better one by peter godman. i believe you can find it on the starship. raf _______________ DB-SIG - SIG on Tabular Databases in Python send messages to: db-sig@python.org administrivia to: db-sig-request@python.org _______________ From aaron@cs.rutgers.edu Mon Feb 23 00:59:50 1998 From: aaron@cs.rutgers.edu (Aaron Watters) Date: Sun, 22 Feb 1998 19:59:50 -0500 Subject: [DB-SIG] ms repositories http://www.summsoft.com/repository/html/vldb97.htm Message-ID: <199802231300.IAA24334@aramis.rutgers.edu> Just thought I'd point out this very interesting repository idea (coming from within the evil empire). The only thing wrong about it that I see is they keep saying "visual basic" where they really mean "python". http://www.summsoft.com/repository/html/vldb97.htm btw: Phil Bernstein is one of the very best database research gods in the known universe. Never met him, but I've read just about everything he's ever typed. Bill or Greg, maybe drop him a line? It's scary the quality of talent MS is acquiring. -- Aaron Watters _______________ DB-SIG - SIG on Tabular Databases in Python send messages to: db-sig@python.org administrivia to: db-sig-request@python.org _______________ From lemburg@uni-duesseldorf.de Wed Feb 25 11:37:37 1998 From: lemburg@uni-duesseldorf.de (M.-A. Lemburg) Date: Wed, 25 Feb 1998 12:37:37 +0100 Subject: [DB-SIG] ANN: DateTime package version 0.7 References: <34F401B7.37EEB0ED@uni-duesseldorf.de> Message-ID: <34F40281.14F5F798@uni-duesseldorf.de> I have uploaded a new version of the DateTime package to starship. It fixes a few minor problems. The interface is quite stable now. Please try it and report any bugs you find: http://starship.skyport.net/~lemburg/mxDateTime.html I would also like to make a DLL for Windows available but have yet to find someone willing to do the necessary setup (should be easy) and compilation. >From the change list: To make the transition from usage of time values to usage of the new types easier, they can convert themselves to floats and integers on demand (e.g. with float() or int()). The DateTime instances return their value in ticks, the DateTimeDelta instances in seconds. The necessary conversion can cause a ConversionError to be raised in case the objects value doesn't fit into the converted types range. Since it is sometimes needed to have the date/time value stored in one number (begin sufficiently accurate to hold a vast range of dates), interfaces to both types were added that return the internal value as days Python float (maps to a C double). The fraction part is calculated using a 86400.0 seconds/day basis and does not account for leap seconds. Fixed a bug in the value of the constant Epoch. The epoch for this module is 1.1.0001 0:00:00.00 and not 1.1.0001 0:00:01.00. Added code from Modules/timemodule.c (found in the 1.5 Python distribution) that allows now() to return fractions of a second. Added __members__ attribute to both types. The module now defines a cleanup function which it registers with Py_AtExit(). This will free the free lists upon finalization of the interpreter. Added #ifdefs and #defines to make the module more portable to platforms which don't provide the C lib functions strftime() and strptime(). These interfaces are only available on platforms which provide the corresponding C functions. You may have to enable them manually (see mxDateTime.c) on platforms other than Unix. When converting the date/time values to the representation used by the C API strftime(), seconds are now rounded to the next integer (the struct tm defines second as being an integer, thus fraction parts can not be displayed). Changed the default date/time representation for str() and repr() to ISO format. I previously used the strftime() C-API but that has the disadvantage of not displaying fractions of a second which can lead to representations off by up to 0.5 seconds. The second attributes of both types now return floats instead of integers. Enjoy ! -- Marc-Andre Lemburg _______________ DB-SIG - SIG on Tabular Databases in Python send messages to: db-sig@python.org administrivia to: db-sig-request@python.org _______________ From lemburg@uni-duesseldorf.de Wed Feb 25 14:08:25 1998 From: lemburg@uni-duesseldorf.de (M.-A. Lemburg) Date: Wed, 25 Feb 1998 15:08:25 +0100 Subject: [DB-SIG] Re: ANN: DateTime package version 0.7 References: <34F401B7.37EEB0ED@uni-duesseldorf.de> <34F40281.14F5F798@uni-duesseldorf.de> Message-ID: <34F425D9.40787FB5@uni-duesseldorf.de> Mark Hammond was so kind to compile the module for usage with Python 1.5 on Windows. I have included the .pyd-file in the archive. If you are on Windows, all you have to do is unzip the archive to a path on your PYTHONPATH and 'import DateTime' will get you going. For the updated archive follow this link: http://starship.skyport.net/~lemburg/mxDateTime.html As per Mark's wish I will include a '.Format()' alias for the method '.strftime' in the next release. That should make the types compatible with the existing COM types and give us a portable way to handle date/time values across platforms. -- Marc-Andre Lemburg _______________ DB-SIG - SIG on Tabular Databases in Python send messages to: db-sig@python.org administrivia to: db-sig-request@python.org _______________ From gstein@lyra.org Thu Feb 26 08:08:07 1998 From: gstein@lyra.org (Greg Stein) Date: Thu, 26 Feb 1998 00:08:07 -0800 Subject: [DB-SIG] ms repositories http://www.summsoft.com/repository/html/vldb97.htm Message-ID: <01BD424A.9E148540.gstein@lyra.org> I've traded several mails with Jason and Brian (two coauthors on the paper). They are currently working in the COM+ group. They are quite aware of Python :). COM+ will essentially enable the automatic persistence of objects' properties. Effectively, this means that when the Python/COM+ bindings are completed, then Python objects should be transparently persistable to the Repository (actually, to various object stores; I'm not currently up on what the underlying API COM+ will use to persist to (e.g. OLE DB)). An interesting question is whether COM+ persistence should look similar to pickling or not (the semantics may be different, so it might not be a great idea to make them similar if they can't be exact). -g p.s. and no... I don't have a date for "completed"... :) It depends mainly on the COM+ dates which are still a ways out. -----Original Message----- From: Aaron Watters [SMTP:aaron@cs.rutgers.edu] Sent: Sunday, February 22, 1998 5:00 PM To: db-sig@python.org Subject: [DB-SIG] ms repositories http://www.summsoft.com/repository/html/vldb97.htm Just thought I'd point out this very interesting repository idea (coming from within the evil empire). The only thing wrong about it that I see is they keep saying "visual basic" where they really mean "python". http://www.summsoft.com/repository/html/vldb97.htm btw: Phil Bernstein is one of the very best database research gods in the known universe. Never met him, but I've read just about everything he's ever typed. Bill or Greg, maybe drop him a line? It's scary the quality of talent MS is acquiring. -- Aaron Watters _______________ DB-SIG - SIG on Tabular Databases in Python send messages to: db-sig@python.org administrivia to: db-sig-request@python.org _______________ _______________ DB-SIG - SIG on Tabular Databases in Python send messages to: db-sig@python.org administrivia to: db-sig-request@python.org _______________