[Zope-DB] RE: Zope-DB digest, Vol 1 #293 - 6 msgs

irtnebznldhh@spammotel.com irtnebznldhh@spammotel.com
Fri, 11 Oct 2002 11:31:57 +0200


> Send Zope-DB mailing list submissions to
> 	zope-db@zope.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.zope.org/mailman/listinfo/zope-db
> or, via email, send a message with subject or body 'help' to
> 	zope-db-request@zope.org
> 
> You can reach the person managing the list at
> 	zope-db-admin@zope.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Zope-DB digest..."
> 
> 
> Today's Topics:
> 
>    1. Oracle/Unicode and Zope problem (Bo M. Maryniuck)
>    2. Re: Oracle/Unicode and Zope problem (Bo M. Maryniuck)
>    3. Re: rollback / commit inside DTML : How To ?? (Harald 
> Koschinski)
>    4. Re: rollback / commit inside DTML : How To ?? (Federico 
> Di Gregorio)
>    5. RE: rollback / commit inside DTML : How To ?? (Smith, 
> Neil (Worcester))
>    6. RE: rollback / commit inside DTML : How To ?? (Federico 
> Di Gregorio)
> 
> --__--__--
> 
> Message: 1
> From: "Bo M. Maryniuck" <b.maryniuk@forbis.lt>
> Reply-To: b.maryniuk@forbis.lt
> To: zope-db@zope.org
> Date: Wed, 9 Oct 2002 20:39:23 +0200
> Subject: [Zope-DB] Oracle/Unicode and Zope problem
> 
> Hi.=20
> 
> I use Oracle Client for Oracle 8i on Linux SuSE 7.1 Pro. My 
> Oracle enviro=
> nment =20
> NLS_LANG for Zope is "AMERICAN_AMERICA.UTF-8". Tables in 
> Oracle are Unico=
> de=20
> UTF-8. When I fetch it with simple ZSQLMethod, I always got 
> ???????? inst=
> ead=20
> cyrillic or baltic or whatever. Somebody know how to solve this?
> 
> --=20
> Regards, Bogdan
> 
> =2E..Unix, MS-DOS, and Windows NT (also known as the Good, 
> the Bad, and
> the Ugly).
> =09=09-- Matt Welsh
> 
> 
> 
> --__--__--
> 
> Message: 2
> From: "Bo M. Maryniuck" <b.maryniuk@forbis.lt>
> Reply-To: b.maryniuk@forbis.lt
> To: zope-db@zope.org
> Subject: Re: [Zope-DB] Oracle/Unicode and Zope problem
> Date: Wed, 9 Oct 2002 20:44:21 +0200
> 
> On Wednesday 09 October 2002 20:39, Bo M. Maryniuck wrote:
> > Hi.
> >
> > I use Oracle Client for Oracle 8i on Linux SuSE 7.1 Pro. My Oracle
> > environment NLS_LANG for Zope is "AMERICAN_AMERICA.UTF-8". 
> Tables in Or=
> acle
> > are Unicode UTF-8. When I fetch it with simple ZSQLMethod, 
> I always got
> > ???????? instead cyrillic or baltic or whatever. Somebody 
> know how to s=
> olve
> > this?
> 
> No sorry, I even can't connect: invalis connection string. 
> ;-) Before the=
> re=20
> was standard Oracle environment, but I just have'nt restart 
> Zope from the=
> =20
> shell to take the changes. But now I can't even login...
> 
> --=20
> Regards, Bogdan
> 
> Inform all the troops that communications have completely broken down.
> 
> 
> 
> --__--__--
> 
> Message: 3
> Date: Thu, 10 Oct 2002 16:59:17 +0200
> From: Harald Koschinski <harald.koschinski@friatec.de>
> Organization: FRIATEC AG
> To: "Matthew T. Kromer" <matt@zope.com>, zope-db <zope-db@zope.org>, 
>  Federico Di Gregorio <fog@initd.org>
> Subject: Re: [Zope-DB] rollback / commit inside DTML : How To ??
> 
> Hi,
> 
> >
> > Agreed -- dont try to abort or commit the transaction *during* the 
> > transaction.  You'll get in a world of hurt if you try.
> 
> Sorry, but I must dissagree -
> the question is: What is a transaction?
> 
> In the case that one REQUEST is one TRANSACTION Zope is doing 
> everything 
> automaticly correct - fine. :-)
> But: If you have some more complicated applications there are several 
> transactions and subtransactions during one REQUEST.
> In the case of a failure you don't want to have a rollback for all 
> transactions - you (I) want to controll which transactions have to 
> commit by hand. :-(
> 
> So I ask my question again: How can I use the python functions for 
> transaction control inside DTML.
> 
> (please don't give the answer, that developing in DTML is a 
> mistake and 
> python is more clever for such complicated application. I use 
> both in a 
> mixed structure but decided to do the database
> transactions in dtml, because zsql is very nice)
> 
> regards
> Harald
> 
> >
> 
> 
> 
> --__--__--
> 
> Message: 4
> Subject: Re: [Zope-DB] rollback / commit inside DTML : How To ??
> From: Federico Di Gregorio <fog@initd.org>
> To: zope-db <zope-db@zope.org>
> Date: 10 Oct 2002 17:07:04 +0200
> 
> 
> --=-1/+LZoLBmaZ4yzCU9RoV
> Content-Type: text/plain
> Content-Transfer-Encoding: quoted-printable
> 
> Il gio, 2002-10-10 alle 16:59, Harald Koschinski ha scritto:
> 
> > But: If you have some more complicated applications there 
> are several=20
> > transactions and subtransactions during one REQUEST.
> > In the case of a failure you don't want to have a rollback 
> for all=20
> > transactions - you (I) want to controll which transactions 
> have to=20
> > commit by hand. :-(
> 
> the plug your code into the zope transaction machinery. doing random
> commits on the Zxxx Connection object is a bad idea because it will
> confuse all the remaining code. also, why don't you rethink your
> application? any zope application that requires multiple 
> commit/rollback
> in a single request looks fragile to me.
> 
> > So I ask my question again: How can I use the python 
> functions for=20
> > transaction control inside DTML.
> >=20
> > (please don't give the answer, that developing in DTML is a 
> mistake and=20
> > python is more clever for such complicated application. I 
> use both in a=20
> > mixed structure but decided to do the database
> > transactions in dtml, because zsql is very nice)
> 
> and doing so you commited yourself to the 1:1 
> REQUEST/TRANSACTION model.
> --=20
> Federico Di Gregorio
> Debian GNU/Linux Developer & Italian Press Contact        
> fog@debian.org
> INIT.D Developer                                           
> fog@initd.org
>                              Best friends are often failed 
> lovers. -- Me
> 
> --=-1/+LZoLBmaZ4yzCU9RoV
> Content-Type: application/pgp-signature; name=signature.asc
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.0 (GNU/Linux)
> 
> iD8DBQA9pZeYvcCgrgZGjesRAhnfAJ4wPMSuZxVCYvVd6PYIKwEVDEQPBwCfY598
> c9OIDWBmvfqrY3KPSMZ9LIc=
> =XCPB
> -----END PGP SIGNATURE-----
> 
> --=-1/+LZoLBmaZ4yzCU9RoV--
> 
> 
> 
> --__--__--
> 
> Message: 5
> From: "Smith, Neil (Worcester)" <Neil.Smith@npower.com>
> To: Harald Koschinski <harald.koschinski@friatec.de>, zope-db
> 	 <zope-db@zope.org>
> Subject: RE: [Zope-DB] rollback / commit inside DTML : How To ??
> Date: Thu, 10 Oct 2002 16:12:35 +0100
> 
> Just create ZSQL methods with a commit and a rollback in 
> them, then call
> them with a dtml-call just like you'd normally do with a SQL method.
> 
> --
> Neil
> 
> -----Original Message-----
> From: Harald Koschinski [mailto:harald.koschinski@friatec.de]
> Sent: 10 October 2002 15:59
> To: Matthew T. Kromer; zope-db; Federico Di Gregorio
> Subject: Re: [Zope-DB] rollback / commit inside DTML : How To ??
> 
> 
> Hi,
> 
> >
> > Agreed -- dont try to abort or commit the transaction *during* the 
> > transaction.  You'll get in a world of hurt if you try.
> 
> Sorry, but I must dissagree -
> the question is: What is a transaction?
> 
> In the case that one REQUEST is one TRANSACTION Zope is doing 
> everything 
> automaticly correct - fine. :-)
> But: If you have some more complicated applications there are several 
> transactions and subtransactions during one REQUEST.
> In the case of a failure you don't want to have a rollback for all 
> transactions - you (I) want to controll which transactions have to 
> commit by hand. :-(
> 
> So I ask my question again: How can I use the python functions for 
> transaction control inside DTML.
> 
> (please don't give the answer, that developing in DTML is a 
> mistake and 
> python is more clever for such complicated application. I use 
> both in a 
> mixed structure but decided to do the database
> transactions in dtml, because zsql is very nice)
> 
> regards
> Harald
> 
> >
> 
> 
> _______________________________________________
> Zope-DB mailing list
> Zope-DB@zope.org
> http://lists.zope.org/mailman/listinfo/zope-db
> **********************************************************************
>  
> The information contained in this e-mail is confidential and 
> intended only for the use of the addressee. If the reader of 
> this message is not the addressee, you are hereby notified 
> that you have received this e-mail in error and you must not 
> copy, disseminate, distribute, use or take any action as a 
> result of the information contained in it.
>     
> If you have received this e-mail in error, please notify 
> postmaster@npower.com (UK 01384 275454) and delete it 
> immediately from your system.
>     
> Neither Npower nor any of the other companies in the Innogy 
> group from whom this e-mail originates accept any 
> responsibility for losses or damage as a result of any 
> viruses and it is your responsibility to check attachments 
> (if any) for viruses.
> 
> Npower Limited
> Registered office: Windmill Hill Business Park, Whitehill 
> Way, Swindon SN5 6PB. Registered in England and Wales: number 3653277
> 
> This e-mail may be sent on behalf of a member of the Innogy 
> group of companies.
> 
> **********************************************************************
> 
> 
> --__--__--
> 
> Message: 6
> Subject: RE: [Zope-DB] rollback / commit inside DTML : How To ??
> From: Federico Di Gregorio <fog@initd.org>
> To: zope-db <zope-db@zope.org>
> Date: 10 Oct 2002 17:19:00 +0200
> 
> 
> --=-69wAwj7qHp+om1yL3Ue8
> Content-Type: text/plain; charset=ISO-8859-15
> Content-Transfer-Encoding: quoted-printable
> 
> Il gio, 2002-10-10 alle 17:12, Smith, Neil (Worcester) ha scritto:
> > Just create ZSQL methods with a commit and a rollback in 
> them, then call
> > them with a dtml-call just like you'd normally do with a SQL method.
> 
> yesss! good. this is the right way blow-up zope transation machinery
> *and* the underlying db adapter (in case of psycopg, for example you
> just *can't* call commit/rollback yourself, but you should use the
> dbapi-2.0 methods to do it.)
> 
> --=20
> Federico Di Gregorio
> Debian GNU/Linux Developer & Italian Press Contact        
> fog@debian.org
> INIT.D Developer                                           
> fog@initd.org
>   All'inizio ho scritto un programma proprietario, in esclusiva per il
>    cliente; =E8 stato tristissimo, perch=E8 mi ha succhiato 
> un pezzo di
>    anima.                                           -- 
> Alessandro Rubini
> 
> --=-69wAwj7qHp+om1yL3Ue8
> Content-Type: application/pgp-signature; name=signature.asc
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.0 (GNU/Linux)
> 
> iD8DBQA9pZpkvcCgrgZGjesRAgGdAKC+Q4sUkqYUfES5GygPGLfGkkdniACgrbtO
> 8j78dSpn/6RFRccn64FFMpA=
> =jqjt
> -----END PGP SIGNATURE-----
> 
> --=-69wAwj7qHp+om1yL3Ue8--
> 
> 
> 
> 
> --__--__--
> 
> _______________________________________________
> Zope-DB mailing list
> Zope-DB@zope.org
> http://lists.zope.org/mailman/listinfo/zope-db
> 
> 
> End of Zope-DB Digest
>