Re: [Zope-dev] ZSQLMethod/Z Database Connection namespace

2002-10-29 Thread Dieter Maurer 
Jeff Coleman writes:
 > I have a product that stores customer information in mysql using
 > ZSQLMethods. 
 > I would like each customer to have a different mysql database (same
 > structure), but all use the same ZSQLMethods for access.
 > So, I tried the following:
 > / - root contains ZSQLMethods and default DB Connector (seems to be
 > required for editing the methods)
 > /CustomerA - contains DB Connector with same name as in root, but uses
 > different mysql database
 > /CustomerB - contains DB Connector with same name as in root, but uses
 > different mysql database
 > 
 > And assumed that /CustomerA/showdata would use the DB Connector in the
 > 'CustomerA' directory, but no matter what it uses the DB Connector in
 > the root directory.  It seems that the ZSQLMethods namespace is put on
 > top and any other DB Connectors are ignored.
 > Is this intentional or a bug?
It is intentional and called "Containment before Context".
Read the acquisition section in

  

to learn more about it.

It was implemented this way mainly because the security framework
should be based on acquisition too, and there, you do not want
that the context can override the security policies defined higher
up in the hierarchy.


Dieter

___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )

Re: [Zope-dev] 2.6.1 Plan?

2002-10-29 Thread Dieter Maurer 
Oliver Bleutgen writes:
 > ...
 > > What do _you_ think 'normal open source practice' is?
 > 
 > 
 > FWIW, see as an example
 > http://developer.kde.org/development-versions/kde-3.0-release-plan.html
 > 
 > and/or
 > http://developer.kde.org/development-versions/kde-3.2-features.html
 > 
 > Seems to work quite well for them.
Almost surely, I am unjust towards the KDE developers:

  I identify the many k* programs with KDE.
  When I do this, then I have never seen that many bugs in the time
  before KDE. My X error log is full of KDE and k* program problems.


Dieter

___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )

[Zope-dev] My 2.6.0 feature patch didn't make it!?

2002-10-29 Thread Brad Clements 
I submitted 2 features to 2.6,

gzip compression

ftp pasv port range spec

the first one made it, the 2nd one didn't.

Both are listed as comitted and vetted  on 

http://dev.zope.org/Wikis/DevSite/Projects/Zope2.6/ProposedFeatures

But the passive port range patch didn't make it into 2.6


 


Brad Clements,[EMAIL PROTECTED]   (315)268-1000
http://www.murkworks.com  (315)268-9812 Fax
AOL-IM: BKClements


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )

Re: [Zope-dev] 2.6.1 Plan?

2002-10-29 Thread Oliver Bleutgen 
Ross J. Reedstrom wrote:



It what world do you live, and can I move there? Every large open source
project I've particpated in or kept track of has had this problem - it's
_really hard_ to turn down cool new patches just because your supposed to
be in feature freeze, trying to get a stable release out.

What do _you_ think 'normal open source practice' is?



FWIW, see as an example
http://developer.kde.org/development-versions/kde-3.0-release-plan.html

and/or
http://developer.kde.org/development-versions/kde-3.2-features.html

Seems to work quite well for them.

cheers,
oliver



___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )

[Zope-dev] ZSQLMethod/Z Database Connection namespace

2002-10-29 Thread Jeff Coleman 
Hi,
I have a product that stores customer information in mysql using
ZSQLMethods. 
I would like each customer to have a different mysql database (same
structure), but all use the same ZSQLMethods for access.
So, I tried the following:
/ - root contains ZSQLMethods and default DB Connector (seems to be
required for editing the methods)
/CustomerA - contains DB Connector with same name as in root, but uses
different mysql database
/CustomerB - contains DB Connector with same name as in root, but uses
different mysql database

And assumed that /CustomerA/showdata would use the DB Connector in the
'CustomerA' directory, but no matter what it uses the DB Connector in
the root directory.  It seems that the ZSQLMethods namespace is put on
top and any other DB Connectors are ignored.
Is this intentional or a bug?

I can patch Shared.DC.ZRDB.DA with the following:

try: nsCid = getattr(aq_parent(self), self.connection_id)
except: ns = self
else: ns = aq_parent(self)

#try: dbc=getattr(self, self.connection_id) <---<<< old code
try: dbc=getattr(ns, self.connection_id)

Is this the only way to solve the problem? 
I hate to add a patch to get what would seem to me to be the correct
functionality.

Thanks,
Jeff

___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )

Re: [Zope-dev] 2.6.1 Plan?

2002-10-29 Thread Ross J. Reedstrom 
On Tue, Oct 29, 2002 at 09:55:40AM +, Chris Withers wrote:
> Chris McDonough wrote:
> >FWIW, the reason that there is a flurry of activity before any release
> >is because people want to see features in a stable release version and
> >by nature (IMHO) programmers are procrastinators. ;-)
> 
> This doesn't fit with normal open source practice. Why are we starting to 
> operate like this?

It what world do you live, and can I move there? Every large open source
project I've particpated in or kept track of has had this problem - it's
_really hard_ to turn down cool new patches just because your supposed to
be in feature freeze, trying to get a stable release out.

What do _you_ think 'normal open source practice' is?

Ross
-- 
Ross Reedstrom, Ph.D. [EMAIL PROTECTED]
Executive Director  phone: 713-348-6166
Gulf Coast Consortium for Bioinformatics  fax: 713-348-6182
Rice University MS-39
Houston, TX 77005

___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )

Re: [Zope-dev] 2.6.1 Plan?

2002-10-29 Thread Chris Withers 
Chris McDonough wrote:

FWIW, the reason that there is a flurry of activity before any release
is because people want to see features in a stable release version and
by nature (IMHO) programmers are procrastinators. ;-)


This doesn't fit with normal open source practice. Why are we starting to 
operate like this?

cheers,

Chris


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )

Re: [Zope-dev] Re: [Zope-Coders] DateTime screwup on 2.6 branch andHEAD

2002-10-29 Thread Chris Withers 
Lennart Regebro wrote:

From: "Casey Duncan" <[EMAIL PROTECTED]>


This is in no way a defense of the release tactics for 2.6.0, but
these types of changes should be done on their own branch and
then merged in atomically to avoid exactly this type of issue.



They were. There were two independant, but related, bugs. Both made in their
own branch, and merged in atomically.


Personally, I'd put this down to bad luck. Bugs are bugs and you don't know 
they're there until you notice them. I don't think there was anything that could 
have reasonably been done to prevent this.

That said, can we see if we can actually get 2.6.1 out within a week (OK, lets 
be sane and say month ;-).

This is open source, lets release early and often...

cheers,

Chris


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )

[Zope-dev] Re: [Zope3-dev] Re: [ZODB-Dev] change date vs. save date

2002-10-29 Thread Chris Withers 
Jim Fulton wrote:

For example, Zope 3 tracks creation and modification times that have 
nothing
to do with database time stamps. 

I agree. Is there any reason for ZODB to actually keep timestamps rather than 
just use serial version ids?

(I understand calls to get the system tiem are expensive, incrementing an 
integer number by one should be somewhat less expensive...)

cheers,

Chris


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )