Hi, I am new to Zope. I started evaluating it a bit to understand its use in our environment. 2 questions concerning the 'portability' of Zope applications: 1- assuming I have 2 Zope servers, one for development and one for deployment: is it possible to port all stuff made in one folder with installation 1 in installation 2 ? ...I would imagine a utility to 'pack' all objects and unpack them in another installation. 2- as to database connectivity (I am used to PHP, where with PHPlib I can write PHP which is portable to setups using different servers). Does the same apply to Zope ? I.e. if I am using ODBC/Access in my 'prototype', and Oracle in my full-blown application, is it sufficient to have a connection ID with the same name to insure portability ? TIA for any feedback. -- ========================================= Andrea Giacomelli Centre for Advanced Studies, Research and Development in Sardinia Environment Group http://www.crs4.it/~andreag =========================================
On Fri, 13 Jul 2001, A. Giacomelli wrote:
1- assuming I have 2 Zope servers, one for development and one for deployment: is it possible to port all stuff made in one folder with installation 1 in installation 2 ? ...I would imagine a utility to 'pack' all objects and unpack them in another installation.
Check the 'Import/Export' button at the bottom of the management screen
2- as to database connectivity (I am used to PHP, where with PHPlib I can write PHP which is portable to setups using different servers).
Does the same apply to Zope ? I.e. if I am using ODBC/Access in my 'prototype', and Oracle in my full-blown application, is it sufficient to have a connection ID with the same name to insure portability ?
Should work just fine, but I've not tested it. bye, Jerome Alet
On Friday 13 July 2001 01:43, A. Giacomelli wrote:
Hi,
I am new to Zope. I started evaluating it a bit to understand its use in our environment.
2 questions concerning the 'portability' of Zope applications:
1- assuming I have 2 Zope servers, one for development and one for deployment: is it possible to port all stuff made in one folder with installation 1 in installation 2 ? ...I would imagine a utility to 'pack' all objects and unpack them in another installation.
as jerome suggested exporting and importing will take care of most of it. ASSUMING you have the same python products installed at both installations. one thing i've started playing around with recently is andy m.'s excellent ZSyncer product which can help you automate this to some degree. http://www.zope.org/Members/andym
2- as to database connectivity (I am used to PHP, where with PHPlib I can write PHP which is portable to setups using different servers).
Does the same apply to Zope ? I.e. if I am using ODBC/Access in my 'prototype', and Oracle in my full-blown application, is it sufficient to have a connection ID with the same name to insure portability ?
well that really depends on what kinda of sql your writing and for what databases. if the sql constructs your using are supported by both dbs than sure, if they're not than you'll have to make adjustments. things like oracle's outer join syntax vs. ansi 92 sql's and how access likes to handle date times will probably need some alteration. cheers kapil
A. Giacomelli writes:
1- assuming I have 2 Zope servers, one for development and one for deployment: is it possible to port all stuff made in one folder with installation 1 in installation 2 ? ...I would imagine a utility to 'pack' all objects and unpack them in another installation. You already have been told about "import/export".
Besides, "ZSyncher" may help you, too.
2- as to database connectivity (I am used to PHP, where with PHPlib I can write PHP which is portable to setups using different servers).
Does the same apply to Zope ? I.e. if I am using ODBC/Access in my 'prototype', and Oracle in my full-blown application, is it sufficient to have a connection ID with the same name to insure portability ? It is no problem from Zope's point of view!
However, there are SQL differences between the various database vendors. Dieter
[A. Giacomelli]
Does the same apply to Zope ? I.e. if I am using ODBC/Access in my 'prototype', and Oracle in my full-blown application, is it sufficient to have a connection ID with the same name to insure portability ?
You can't count on Oracle and Access being fully compatible in their syntax, even using odbc. Each and every query will have to be checked. It may or may not work without changes, depending of course on those pesky details. Even the connection string may turn out to be different so a connection with the same name may or may not work, either. In other words, test before committing. On the other hand, they'll probably be ***close***, so it won't be like starting from scratch again even if things don't quite work. Cheers, Tom P
participants (5)
-
A. Giacomelli -
Dieter Maurer -
ender -
Jerome Alet -
Thomas B. Passin