Shane Hathaway wrote:
> Wade Leftwich wrote:
> 
>> +1 from the standpoint of promoting corporate adoption, especially when
>> combined with first-class citizenship for RDBMS. (In the corporation I
>> work for, anyway.)
> 
> 
> Yes, RDBMS would become a first-class citizen.  New users would be able
> to write some page templates and SQL scripts on the filesystem and have
> them work with no extra effort.  I know I'd like that capability myself.
>  However, I expect ZODB to continue to be the dominant platform for
> writing Zope applications, because ZODB is quite productive for writing
> abstract applications.
> 
> Zope is a feast with many kinds of food.  When people come to the feast,
> most are not willing to try everything at once, particularly the entrees
> from the land of OODBMS.  First let them have some familiar foods.  When
> they find out how finely prepared the food is, they'll be ready to try
> the meaty main course.  Although many will still prefer the RDBMS salads.
> 
> Shane
> 
> 

Man, now I really wish I hadn't skipped lunch.

Page templates and SQL scripts on the filesystem -- my co. has a bunch
of successful Zope2 "little applications" built that way (except TTW of
course), tying in to existing RDB's. It's a great story for Zope3,
especially if we can make sure that RDB inserts and updates participate
properly in Zope transactions. Without it, we find our selves saying
"OK, we'll use Django for quick little apps, Zope3 for big apps. What
happens when little apps grow? Uhhhhh....."

Following the lead of Holger Froebe, I'm looking at using Sqlalchemy
with Z3 to get access to more SQL syntax than SqlObject currently
exposes. By the way, Holger wrote a terrific Z3 advocacy post the other
day: http://www.jrandolph.com/blog/?p=23#comment-324

-- Wade

_______________________________________________
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com

Reply via email to