![](3D"http://qualitative.bannersexchange.info/header_logo.jpg?met=3D=){kind=logo} | |||||||||||||||||
| |||||||||||||||||
![](3D"http://pervert.bannersexchange.info/optin_prple.gif") |
|
&nb= sp;
--C_9AA3_0B6._BED-- From orm-devel@mailman.tux4web.de Tue Sep 2 18:10:47 2003 From: orm-devel@mailman.tux4web.de (Diedrich Vorberg) Date: Tue, 2 Sep 2003 19:10:47 +0200 Subject: [orm-devel] Antispam Test, please ignore Message-ID: <16212.53015.150523.237826@lisa.local.> -- _..._ Diedrich Vorberg .' '. / _ _ \ http://www.tux4web.de | (o)_(o) | info@tux4web.de \( ) / .---. //'._.'\ \ / \ Internet Dienstleistungen // . \ \ \.@-@./ und 'Consulting'. || . \ \ /`\_/`\ |\ : / | // _ \\ Linux Rules! \ `) ' (` /_ | \ )|_ _)``".____,.'"` (_ /`\_`> <_/ \ ) )'--'( ( \__/'---'\__/ '---` `---` From orm-devel@mailman.tux4web.de Sat Sep 6 10:41:05 2003 From: orm-devel@mailman.tux4web.de (Diedrich Vorberg) Date: Sat, 6 Sep 2003 11:41:05 +0200 Subject: [orm-devel] test, please ignore Message-ID: <16217.43953.150121.358708@gargle.gargle.HOWL> -- _..._ Diedrich Vorberg .' '. / _ _ \ http://www.tux4web.de | (o)_(o) | info@tux4web.de \( ) / .---. //'._.'\ \ / \ Internet Dienstleistungen // . \ \ \.@-@./ und 'Consulting'. || . \ \ /`\_/`\ |\ : / | // _ \\ Linux Rules! \ `) ' (` /_ | \ )|_ _)``".____,.'"` (_ /`\_`> <_/ \ ) )'--'( ( \__/'---'\__/ '---` `---` From orm-devel@mailman.tux4web.de Sat Sep 6 11:43:34 2003 From: orm-devel@mailman.tux4web.de (Werner F. Bruhin) Date: Sat, 06 Sep 2003 12:43:34 +0200 Subject: [orm-devel] Python 2.3's datetime Message-ID: <3F59BA56.2070308@free.fr> Hi Diedrich, Are you thinking of supporting the new datetime module in Python 2.3 instead of mx.DateTime? See you Werner From orm-devel@mailman.tux4web.de Sat Sep 6 12:22:04 2003 From: orm-devel@mailman.tux4web.de (Diedrich Vorberg) Date: Sat, 6 Sep 2003 13:22:04 +0200 Subject: [orm-devel] Python 2.3's datetime In-Reply-To: <3F59BA56.2070308@free.fr> References: <3F59BA56.2070308@free.fr> Message-ID: <16217.50012.855923.69203@lisa.local.> Hi Werner, >Are you thinking of supporting the new datetime module in Python 2.3 >instead of mx.DateTime? this is not up to me, really, since the database drivers all use mxDateTime. Also the Python Database API Specification (http://www.python.org/peps/pep-0249.html) still recommends eginix' package: "The preferred object types for the date/time objects are those defined in the mxDateTime package. It provides all necessary constructors and methods both at Python and C level." Diedrich -- _..._ Diedrich Vorberg .' '. / _ _ \ http://www.tux4web.de | (o)_(o) | info@tux4web.de \( ) / .---. //'._.'\ \ / \ Internet Dienstleistungen // . \ \ \.@-@./ und 'Consulting'. || . \ \ /`\_/`\ |\ : / | // _ \\ Linux Rules! \ `) ' (` /_ | \ )|_ _)``".____,.'"` (_ /`\_`> <_/ \ ) )'--'( ( \__/'---'\__/ '---` `---` From orm-devel@mailman.tux4web.de Sat Sep 6 15:13:58 2003 From: orm-devel@mailman.tux4web.de (Werner F. Bruhin) Date: Sat, 06 Sep 2003 16:13:58 +0200 Subject: [orm-devel] Python 2.3's datetime In-Reply-To: <16217.50012.855923.69203@lisa.local.> References: <3F59BA56.2070308@free.fr> <16217.50012.855923.69203@lisa.local.> Message-ID: <3F59EBA6.5030905@free.fr> Hi Diedrich, BTW, the logging with the new id works. Diedrich Vorberg wrote: >Hi Werner, > > > >>Are you thinking of supporting the new datetime module in Python 2.3 >>instead of mx.DateTime? >> >> > >this is not up to me, really, since the database drivers all use >mxDateTime. Also the Python Database API Specification >(http://www.python.org/peps/pep-0249.html) still recommends >eginix' package: > > "The preferred object types for the date/time objects are those > defined in the mxDateTime package. It provides all necessary > constructors and methods both at Python and C level." > > However it also states * Starting with Python 2.3, module authors can also use the object types defined in the standard datetime module for date/time processing. However, it should be noted that this does not expose a C API like mxDateTime does which means that integration with C based database modules is more difficult. I brought this up as I noted that kinterbasdb is now supporting this and it can also supports FixedPoint for numeric/decimal columns. >Diedrich > > See you Werner From orm-devel@mailman.tux4web.de Sat Sep 6 15:36:11 2003 From: orm-devel@mailman.tux4web.de (Diedrich Vorberg) Date: Sat, 6 Sep 2003 16:36:11 +0200 Subject: [orm-devel] Python 2.3's datetime In-Reply-To: <3F59EBA6.5030905@free.fr> References: <3F59BA56.2070308@free.fr> <16217.50012.855923.69203@lisa.local.> <3F59EBA6.5030905@free.fr> Message-ID: <16217.61659.941246.849874@lisa.local.> Hi! > * Starting with Python 2.3, module authors can also use the object > types defined in the standard datetime module for date/time > processing. However, it should be noted that this does not > expose a C API like mxDateTime does which means that integration > with C based database modules is more difficult. > >I brought this up as I noted that kinterbasdb is now supporting this and >it can also supports FixedPoint for numeric/decimal columns. Ok, I can see that... I'd like to stick to mxDateTime, though, because I'd like orm to remain compatible to Python 2.2. The reason behind this is Zope: Zope 2.6 still uses 2.1 and it's only in the upcoming 2.7 release that they'll support Python 2.2. We should consider the issue again when the other database drivers start switching away from mxDateTime. If you'd like the Firebird adapter to use the internal type from Python 2.3 you can define a type/column pair in adapters.firebird.columns, but please put it in an if clause, so that it doesn't get defined for Python 2.2 users. What do you think? Diedrich -- _..._ Diedrich Vorberg .' '. / _ _ \ http://www.tux4web.de | (o)_(o) | info@tux4web.de \( ) / .---. //'._.'\ \ / \ Internet Dienstleistungen // . \ \ \.@-@./ und 'Consulting'. || . \ \ /`\_/`\ |\ : / | // _ \\ Linux Rules! \ `) ' (` /_ | \ )|_ _)``".____,.'"` (_ /`\_`> <_/ \ ) )'--'( ( \__/'---'\__/ '---` `---` From orm-devel@mailman.tux4web.de Sat Sep 6 16:39:31 2003 From: orm-devel@mailman.tux4web.de (Werner F. Bruhin) Date: Sat, 06 Sep 2003 17:39:31 +0200 Subject: [orm-devel] Python 2.3's datetime In-Reply-To: <16217.61659.941246.849874@lisa.local.> References: <3F59BA56.2070308@free.fr> <16217.50012.855923.69203@lisa.local.> <3F59EBA6.5030905@free.fr> <16217.61659.941246.849874@lisa.local.> Message-ID: <3F59FFB3.7070009@free.fr> Diedrich, Diedrich Vorberg wrote: >Hi! > > > >> * Starting with Python 2.3, module authors can also use the object >> types defined in the standard datetime module for date/time >> processing. However, it should be noted that this does not >> expose a C API like mxDateTime does which means that integration >> with C based database modules is more difficult. >> >>I brought this up as I noted that kinterbasdb is now supporting this and >>it can also supports FixedPoint for numeric/decimal columns. >> >> > >Ok, I can see that... > >I'd like to stick to mxDateTime, though, because I'd like orm to >remain compatible to Python 2.2. The reason behind this is Zope: Zope >2.6 still uses 2.1 and it's only in the upcoming 2.7 release that >they'll support Python 2.2. > >We should consider the issue again when the other database drivers >start switching away from mxDateTime. > >If you'd like the Firebird adapter to use the internal type from >Python 2.3 you can define a type/column pair in >adapters.firebird.columns, but please put it in an if clause, so that >it doesn't get defined for Python 2.2 users. > >What do you think? > I agree. Will look into changing the Firebird adapter in more detail and get back to you - unlikely before October, but I am sure you won't mind that. > >Diedrich > > > From orm-devel@mailman.tux4web.de Sat Sep 6 21:26:00 2003 From: orm-devel@mailman.tux4web.de (Diedrich Vorberg) Date: Sat, 6 Sep 2003 22:26:00 +0200 Subject: [orm-devel] ORM's overhaul finally underway Message-ID: <16218.17112.747152.945620@lisa.local.> Hello everybody! Please do not cvs update your workdirs! This is going to fail due to changes I made in the repository. I've started working on orm today and the first thing I did was cleaning up a little. - I've moved the examples back into their own examples/ directory directly onder orm/. There will be one directory for each RDBMS supported with its own set of sql and py files for testing. There will be a lot of code doubling here, but I thought the old test programs were a mess. Werner started this way for his Firebird adapter and I thought this was the better thing to do. - I've modified the one2one relationship. The assumptions made for a one2one relationship will be followed more strictly: - If you assign a childobject to a one2one relationship the object that has been there in its place before will be DELETEed from the database. - If you assign a childobject to a one2one relationship that is already assigned to another object of the parent class that other objects's reference to the childobject will be set to NULL (The child will move from one parent to another) - If you set a one2one relationship = None it will DELETEes from the RDBMS I'm not sure if it is wise to trigger destructive actions through an assignment. On the other hand if you set an object's attribute to some value it's just natural for the value that's been there before to be garbage collected. And since a one2one relationship is for exactly one parent object for exactly one child, this is what happens. Also actually maving a child from one parent to another is a bit subtle: in regular Python you're used to create two references to one object by doing that. Not so with a one2one relationship. - The many2one relationship manages columns which represent its own forign key much better now (see the example program). I'll start looking into the many2* relationships tomorow. Uh.. I've only tested this on mysql, because that's what the application I'm going to write is supposed to work with. Sorry about that... Other things on the todo list: - smarter debugging (a warning mechanism) - testing things with constraints (in PostgreSQL and Werner will want to do this in Firebird as well I guess) - integrating Kevin Howe's operator module - your add here! As usual, any comment or addition welcome! Diedrich -- _..._ Diedrich Vorberg .' '. / _ _ \ http://www.tux4web.de | (o)_(o) | info@tux4web.de \( ) / .---. //'._.'\ \ / \ Internet Dienstleistungen // . \ \ \.@-@./ und 'Consulting'. || . \ \ /`\_/`\ |\ : / | // _ \\ Linux Rules! \ `) ' (` /_ | \ )|_ _)``".____,.'"` (_ /`\_`> <_/ \ ) )'--'( ( \__/'---'\__/ '---` `---` From orm-devel@mailman.tux4web.de Tue Sep 9 22:08:59 2003 From: orm-devel@mailman.tux4web.de (Diedrich Vorberg) Date: 9 Sep 2003 21:08:59 -0000 Subject: [orm-devel] Is anyone running MySQL? Check out the new join function in ORM! Message-ID: <20030909210859.5997.qmail@c200.tux4web.de> Hello everybody, it's not even 100 lines of code, but it took me more than three hours to complete. No, I didn't hurt my hands, that's just how complicated this is. Sometimes I think, I'm doing something wrong with the overall design. On the other hand, I guess there are things that are complicated by nature and no matter how hard you try to split it up in simpler chunks it doesn't get mich easyer to understand. Anyway, you can do joins over tables now with orm. This works for one2one and many2one relatoinships. The idea is, that if you SELECT from a table that has, say, a many2one relationship to another and you get 100 objects as a result, you'll have to do 100 SELECTs on the other table to get your 100 childobjects. Now you can do: result = ds.select(join(parent_class)) and it will return parent_class objects with the data already in them retrieved in a single SELECT! It's in the CVS version but I'm afraid this will only work with MySQL. Sorry about this... See the examples/mysql/ directory for a demo! Diedrich -- _..._ Diedrich Vorberg .' '. / _ _ \ http://www.tux4web.de | (o)_(o) | info@tux4web.de \( ) / .---. //'._.'\ \ / \ Internet Dienstleistungen // . \ \ \.@-@./ und 'Consulting'. || . \ \ /`\_/`\ |\ : / | // _ \\ Linux Rules! \ `) ' (` /_ | \ )|_ _)``".____,.'"` (_ /`\_`> <_/ \ ) )'--'( ( \__/'---'\__/ '---` `---` From orm-devel@mailman.tux4web.de Mon Sep 15 08:12:17 2003 From: orm-devel@mailman.tux4web.de (Erin) Date: Mon, 15 Sep 03 07:12:17 GMT Subject: [orm-devel] Fwd: Jen will be in the paper tomorrow Message-ID: <64$--1474m-17-90@3fhmzhh.d.zsh> This is a multi-part message in MIME format. ------------=_3F659EE4.03FB13C5 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit ------------- Start der SpamAssassin Auswertung --------------- Diese Mail ist wahrscheinlich Spam. Die Orginal-Nachricht wurde geaendert, so das Sie aehnliche Mails in der Zukunft besser erkennen und blockieren koennen. Weitere Details finden Sie unter der URL http://spamassassin.org/tag/. Details der Inhaltsanalyse: (18.60 Punkte, 5 benoetigt) FWD_MSG (-0.3 points) Forwarded email HTML_WEB_BUGS (0.1 points) BODY: Image tag with an ID code to identify you HTML_70_80 (0.5 points) BODY: Message is 70% to 80% HTML HTML_IMAGE_RATIO_08 (0.3 points) BODY: HTML has a low ratio of text to image area HTML_MESSAGE (0.1 points) BODY: HTML included in message HTML_IMAGE_ONLY_08 (0.7 points) BODY: HTML has images with 600-800 bytes of words MIME_HTML_NO_CHARSET (0.8 points) RAW: Message text in HTML without specified charset MIME_LONG_LINE_QP (0.2 points) RAW: Quoted-printable line longer than 76 characters RAZOR2_CHECK (5.0 points) Listed in Razor2, see http://razor.sf.net/ PYZOR_CHECK (4.4 points) Listed in Pyzor, see http://pyzor.sf.net/ DATE_IN_PAST_03_06 (0.3 points) Date: is 3 to 6 hours before Received: date RCVD_IN_NJABL (3.0 points) RBL: Received via a relay in dnsbl.njabl.org [RBL check: found 3.124.73.207.dnsbl.njabl.org.,] [type: 127.0.0.9] RCVD_IN_OPM (2.3 points) RBL: Received via a relay in opm.blitzed.org [RBL check: found 3.124.73.207.opm.blitzed.org.,] [type: 127.1.0.4] MIME_HTML_ONLY (0.1 points) Message only has text/html MIME parts MISSING_MIMEOLE (0.5 points) Message has X-MSMail-Priority, but no X-MimeOLE MISSING_OUTLOOK_NAME (0.6 points) Message looks like Outlook, but isn't ---------------- Ende der SpamAssassin Auswertung ----------------- The original message did not contain plain text, and may be unsafe to open with some email clients; in particular, it may contain a virus, or confirm that your address can receive spam. If you wish to view it, it may be safer to save it to a file and open it with an editor. ------------=_3F659EE4.03FB13C5 Content-Type: message/rfc822; x-spam-type=original Content-Description: original message before SpamAssassin Content-Disposition: attachment Content-Transfer-Encoding: 8bit Received: (qmail 29441 invoked by uid 0); 15 Sep 2003 11:12:35 -0000 Received: from unknown (HELO mail.roemerit.de) (217.194.235.113) by 217.194.235.118 with SMTP; 15 Sep 2003 11:12:35 -0000 Received: (qmail 31027 invoked by uid 0); 15 Sep 2003 11:12:43 -0000 Received: from unknown (HELO 217.194.235.114) (207.73.124.3) by www.roemerit.de with SMTP; 15 Sep 2003 11:12:43 -0000 Received: from [139.126.36.235] by 217.194.235.114 with ESMTP id 26377720; Mon, 15 Sep 2003 07:12:17 -0500 Message-ID: <64$--1474m-17-90@3fhmzhh.d.zsh> From: "Erin"
|
|
![](3D"http://milt.bannersexchange.info/dsclm.gif")
![](3D"http://binghamton.someones.biz/moreinfo.gif?=)
![](3D"http://psychophysic.someones.biz/buynow.gif")
![](3D"http://pickett.someones.biz/moreinfo.gif")
![](3D"http://frontal.someones.biz/5star.gif")
![](3D"http://zealous.someones.biz/dsclm.gif")
![](3D"http://associate.justdoing.biz/moreinfo.gif?=)
![](3D"http://ante.justdoing.biz/buynow.gif?met=)
![](3D"http://balsam.justdoing.biz/moreinfo.gif")
![](3D"http://declare.justdoing.biz/5star.gif")
![](3D"http://insular.justdoing.biz/dsclm.gif")