- Zope - Zope lists

RE: [Zope] - Multiple database files
by Rob Page 07 Jan '99

07 Jan '99

> I was thinking of some of my development problems with Zope -- for > example, it's difficult to work on code at home, tar it up, bring it > to work and change it some more, take it home again ... -- and > realized that being able to split up the object database into multiple > files could help. Imagine if you could have several Data.bbb files, > each holding some subset of the database's objects. This might be > done by specifying into which file an object goes; the object's > children go into the same file, unless they're explicitly moved into > another file. Independent of implementation concerns (boy, that was easy!) I agree. I'd also like to see that woven into sessions. Specifically, I'd like to check out a sub-tree to a file, take it on the road and tweak it. Since I've got the folder in a session I would essentially have it locked for writing. When I got back I would replay the transactions into the main site. --Rob

3 2

- Some DateTime behaviors I just don't understand
by skip＠calendar.com 07 Jan '99

07 Jan '99

I tried: dt = DateTime.DateTime(time.time()) dt.timeTime() and got just what I expected: 915677129.19 I then tried dt = DateTime.DateTime(0.0) dt.timeTime() and got a traceback: Traceback (innermost last): File "<stdin>", line 1, in ? File "DateTime/DateTime.py", line 874, in timeTime raise self.DateTimeError,'No time module compatible time to return' DateTimeError: No time module compatible time to return Surely 0.0 is a valid time module compatible time: time.gmtime(0.0) (1970, 1, 1, 0, 0, 0, 3, 1, 0) Can I not initialize a DateTime object to the Unix epoch? I tried several multiples of 10.0 and didn't avoid the traceback until I tried dt = DateTime.DateTime(100000.0) which is somewhat more than one day more recent than gmtime(0.0). There's apparently some magnitude-dependent interpretation of single numeric initializers, but the documentation file in the package is unclear on how it distinguishes between the two interpretations: A DateTime object is returned that represents either the gmt value of the time.time() float represented in the local machine's timezone, or that number of days after January 1, 1901. Note that the number of days after 1901 need to be expressed from the viewpoint of the local machine's timezone. A negative argument will yield a date-time value before 1901. While horsing around some more, I got some other strange behavior as well: >>> time.gmtime(24*60*60) (1970, 1, 2, 0, 0, 0, 4, 2, 0) >>> dt = DateTime.DateTime(24*60*60) >>> dt.timeTime() 86400 >>> dt = DateTime.DateTime(24*60*50) >>> dt.timeTime() 72000 >>> dt = DateTime.DateTime(24*60*40) >>> dt.timeTime() 57600 >>> dt = DateTime.DateTime(24*60*30.0) Traceback (innermost last): File "<stdin>", line 1, in ? File "DateTime/DateTime.py", line 513, in __init__ s=(_j-int(_j))*86400.0 OverflowError: float too large to convert >>> dt.timeTime() 57600 >>> dt = DateTime.DateTime(24*60*30) Traceback (innermost last): File "<stdin>", line 1, in ? File "DateTime/DateTime.py", line 513, in __init__ s=(_j-int(_j))*86400.0 OverflowError: float too large to convert Why would I be getting overflow errors as the numbers got smaller? Skip Montanaro | Mojam: "Uniting the World of Music" http://www.mojam.com/ skip(a)calendar.com | Musi-Cal: http://concerts.calendar.com/ 518-372-5583

4 8

- A test. Delete me
by Robert O'Connor 07 Jan '99

07 Jan '99

Checking to see if list is active. I subscribed yesterday and no messages seen yet.

1 0

- strftime for DateTime
by skip＠calendar.com 07 Jan '99

07 Jan '99

The appended context diff seems to do what Jim asked for. Here's a simple session: >>> import DateTime, time >>> dt = DateTime.DateTime(time.time()) >>> dt.strftime("%Y-%m-%d") '1999-01-07' >>> getattr(dt, "%Y-%m-%d") <DateTime.DateTime.strftimeFormatter instance at 8116570> >>> getattr(dt, "%Y-%m-%d")() '1999-01-07' (Jim actually did all the work. I made sure the necessary time functions were available at the module level and generated a context diff... :-) Skip Montanaro | Mojam: "Uniting the World of Music" http://www.mojam.com/ skip(a)calendar.com | Musi-Cal: http://concerts.calendar.com/ 518-372-5583 *** /tmp/DateTime.py.~1~ Wed Jan 6 20:00:11 1999 --- /tmp/DateTime.py Wed Jan 6 20:00:11 1999 *************** *** 101,107 **** import sys,os,regex,DateTimeZone from string import strip,split,upper,lower,atoi,atof,find,join ! from time import time,gmtime,localtime,asctime,tzname from types import InstanceType,IntType,FloatType,StringType --- 101,107 ---- import sys,os,regex,DateTimeZone from string import strip,split,upper,lower,atoi,atof,find,join ! from time import time,gmtime,localtime,asctime,tzname,strftime,mktime from types import InstanceType,IntType,FloatType,StringType *************** *** 854,859 **** --- 854,862 ---- def _validTime(self,h,m,s): return h>=0 and h<=23 and m>=0 and m<=59 and s>=0 and s<=59 + def __getattr__(self, name): + if '%' in name: return strftimeFormatter(self, name) + raise AttributeError, name # Conversion and comparison methods *************** *** 1117,1122 **** --- 1120,1127 ---- """Return the second""" return self._second + def strftime(self, format): + return strftime(format, gmtime(self.timeTime())) # General formats from previous DateTime *************** *** 1294,1299 **** --- 1299,1312 ---- """Convert to floating-point number of days since Jan. 1, 1901 (gmt)""" return float(self._d) + + class strftimeFormatter: + + def __init__(self, dt, format): + self._dt=dt + self._f=format + + def __call__(self): return self._dt.strftime(self._f) # Module methods

3 4

RE: [Zope] - Convert database date to Zope date
by Jeff Bauer 06 Jan '99

06 Jan '99

> I was wondering that myself. Does MySQL have any sort of > Date type? Yes, the MySQL DATE type uses YYYY-MM-DD syntax, and also understands YY-MM-DD and YYMMDD. Range 0000-00-00 to 9999-12-31. It also has a DATETIME type in "YYYY-MM-DD HH:MM:SS" format. Same range as DATE. Regards, Jeff Bauer Rubicon, Inc.

1 0

- Zope Solid Database Adapter is available for testing
by Jim Fulton 06 Jan '99

06 Jan '99

Hi, I've put together a beta release of a Zope Solid Database Adapter (for the Solid Database) at: http://www.zope.org/Download/ZSolidDA/ I'd appreciate comments and bug reports before I make a final release. Note: This DA uses a SWIGed extension module, sql.c. This release includes the source, which happens also to be the source of the ODBC DA (ZODBCDA). I assume that this could be readily adapted to other databases that provide an ODBC interface, such as Adabase. I also suspect that we will eventually replace this DA with one maded on mxODBC. Jim -- Jim Fulton mailto:jim@digicool.com Technical Director (888) 344-4332 Python Powered! Digital Creations http://www.digicool.com http://www.python.org Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email address may not be added to any commercial mail list with out my permission. Violation of my privacy with advertising or SPAM will result in a suit for a MINIMUM of $500 damages/incident, $1500 for repeats.

1 0

RE: [Zope] - Problem adding object on Win32 binary release
by Brian Lloyd 06 Jan '99

06 Jan '99

> At 09:30 AM 12/28/98 -0500, you wrote: > > >> Unfortunately Zope doesn't work with my favourite browser > >> (Opera), so I > > > >I see that Opera doesnt seem to like forms with an > >ENCTYPE specified -- is this what you are referring > >to? (e.g. I can add Folders with Opera, but it seems > >to hang waiting for a response when adding documents, > >images or files which have file upload fields. Interestingly, > >the document _does_ get created in Zope - I'll look into > >this). > > Actually, I get an error the minute I go into the management screens > stating "The server requested a login authentication method > that Opera does > not yet support." That's with Opera v3.5 That's odd - I'm using 3.2 on NT and have no problems with authentication :( Brian Lloyd brian(a)digicool.com Software Engineer 540.371.6909 Digital Creations http://www.digicool.com

5 4

- Test: Deleteme: First Message.
by Robert O'Connor 06 Jan '99

06 Jan '99

Test: Deleteme: First Message. -BOBO 'Connor ;-)

1 0

- Zope/ODBC and MS Sql Server 6.5 connection
by Kiss, Arpad 06 Jan '99

06 Jan '99

Hi! I couldn't connect to Sql Server 6.5 too. I looked at db.py (line 160-164 contains the important things) and ODBC log file and I found that: * the Zope uses SQLConnect function. It has three parameters: DSN, UID and AuthStr * db.py uses string.split(connect string), so we have to type in the connect string: dsn userid password. I tested it with Oracle and Access ODBC driver and it works. * but it doesn't work with SQL Server 6.5 driver, because in this case SQLConnect returns SQL_SUCCESS_WITH_INFO (=1) instead of SQL_SUCCESS(=0) and I suppose Zope handles it as it returns SQL_ERROR(=-1). I have found this in the SQL Server 6.5 driver help: SQLConnect retrieves the value of the LANGUAGE keyword from the ODBC data source definition. If the SQL Server driver is unable to use the specified language, it uses the default language for the specified user ID, and SQLConnect returns SQL_SUCCESS_WITH_INFO. If SQL Server is unable to use the default language for the specified user ID, SQLConnect returns SQL_ERROR. SQLConnect retrieves the value of the DATABASE keyword from the ODBC data source definition. If the SQL Server driver is unable to use the specified database, it uses the default database for the specified user ID, and SQLConnect returns SQL_SUCCESS_WITH_INFO. If SQL Server is unable to use the default database for the specified user ID, SQLConnect returns SQL_ERROR. In the ODBC data source definition I set the LANGUAGE and DATABASE to the defaults of the specified user ID but it couldn't help. Perhaps there is someone out who can help us based on the above pice of information. Thanks in advanvce: ¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤ Kiss Árpád akiss(a)geometria.hu ¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤

1 0

RE: [Zope] - Problem with pcgi on FreeBSD 2.2.8/Python 1.5.1
by Jeff Bauer 06 Jan '99

06 Jan '99

> Zope.cgi > Bad system call (core dumped) > /* > // pcgiStartProc: manages starting a pcgi resource. > */ > #ifdef UNIX > int pcgiStartProc(pcgiResource *r) > { > > [ lots of code deleted.....] > > /* Make sure another wrapper isn't already doing a restart */ [ dies here.... ] > if ((r->lock=semget(101, 1, 0700 | IPC_CREAT | IPC_EXCL)) == -1) > > [ more code deleted .....] Steve, Can you send Brian Lloyd and me the FreeBSD man pages on semget and semctl? Or better yet, point us to a browsable man page site for FreeBSD. Best regards, Jeff Bauer Rubicon, Inc.

2 1