Hi I am about to go stark, raving, frothing mad with the DTML-IN batching. Is there a known (or unknown) bug with this? I have searched and read everything I can find about this and no luck. The problem is with carrying the query terms over from one batch page to the next. Right now I am using the script found here: http://mail.zope.org/pipermail/zope-collector-monitor/2003-May/002001.ht ml Except I changed, <dtml-let batch="_.range(100, 180)" batch_size="10" batch_start="REQUEST.get('batch_start',1)"> To <dtml-let batch="myZSQLMethod1" batch_size="10" batch_start="REQUEST.get('batch_start',1)"> The mySQLMethod1 takes two params which the search form supplies to REQUEST. This works great. The pagination works beautifully. However, when I use the very same result script with myZSQLMethod2 (same DB table), which takes 5 params (all optional) the pagination breaks and no-longer passes the query terms. I have checked and rechecked both scripts and both forms. The ZSQLMethods both test good. I am out of ideas. For the life of me I cannot figure out why I'm losing my query terms in one and not the other when the two are almost identical. Care to enlighten me with your collective wisdom? Zope 2.9.6 with mxODBCDA SQL Server 2K PostgreSQL 8.2 Windows XP :-( M. A. Ruberto (Programmer) Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.
----- Original Message ----- From: "Programmer" <programmer@paradigm-corp.com> To: <zope@zope.org> Sent: Wednesday, May 30, 2007 4:44 PM Subject: [Zope] a batch of inSaNitY!
Hi
I am about to go stark, raving, frothing mad with the DTML-IN batching. Is there a known (or unknown) bug with this?
I have searched and read everything I can find about this and no luck. The problem is with carrying the query terms over from one batch page to the next. Right now I am using the script found here: http://mail.zope.org/pipermail/zope-collector-monitor/2003-May/002001.ht ml
Except I changed,
<dtml-let batch="_.range(100, 180)" batch_size="10" batch_start="REQUEST.get('batch_start',1)">
To
<dtml-let batch="myZSQLMethod1" batch_size="10" batch_start="REQUEST.get('batch_start',1)">
The mySQLMethod1 takes two params which the search form supplies to REQUEST. This works great. The pagination works beautifully. However, when I use the very same result script with myZSQLMethod2 (same DB table), which takes 5 params (all optional) the pagination breaks and no-longer passes the query terms. I have checked and rechecked both scripts and both forms. The ZSQLMethods both test good. I am out of ideas. For the life of me I cannot figure out why I'm losing my query terms in one and not the other when the two are almost identical. Care to enlighten me with your collective wisdom?
In similar situations I have done the following: 1) call a python script/external method which: (i) does the db search; (ii) formats the results as required for display; (iii) returns a tuple that contains: list of search results, url parameters for 'previous' link; url parameters for 'next' link; url parameters for 'first link'; url parameters for 'last' link 2) use a dtml method to call the script/ext.method like <dtml-let rStat="mySearchRoutine(parm1, parm1, ...)"> <dtml-in "rStat[0]"> display code here eg. <dtml-var sequence-item><br> or could be an html/css table, etc. <dtml-if sequence-end> <a href="...?<dtml-var "rStat[1]">">previous</a> <a href="...?<dtml-var "rStat[2]">">next</a> <a href="...?<dtml-var "rStat[3]">">first</a> <a href="...?<dtml-var "rStat[4]">">last</a> </dtml-if> </dtml-in> </dtml-let> This greatly simplifies the dtml and facilitates debugging and future modifications. hth Jonathan
Hi Jonathan, I have something similar to your idea already. The python script supplies page number to a stored procedure which handles the actual paging. The script takes the result from the proc and builds an html table and handles column sorting on the table. The output of the script is just a single variable so I can just use &dtml-var instead of the flaky &dtml-in. Problem I have now is this new search interface makes use of full-text searching on SQL Server 2K. The paging proc wasn't written to handle it and will need to be rewritten from scratch. This will take a lot of time and testing. I thought I could slap something simple and fast together to use in the interim to allow people to start testing the search engine. I really do wish Zope would either fix or eliminate broken features. At the very least have the curtesy to say "hey y'all, this is broke, don't bother" so folks don't waste time with it. Mike -----Original Message----- From: Jonathan [mailto:dev101@magma.ca] Sent: Wednesday, May 30, 2007 5:22 PM To: Programmer; zope@zope.org Subject: Re: [Zope] a batch of inSaNitY! ----- Original Message ----- From: "Programmer" <programmer@paradigm-corp.com> To: <zope@zope.org> Sent: Wednesday, May 30, 2007 4:44 PM Subject: [Zope] a batch of inSaNitY!
Hi
I am about to go stark, raving, frothing mad with the DTML-IN batching. Is there a known (or unknown) bug with this?
I have searched and read everything I can find about this and no luck. The problem is with carrying the query terms over from one batch page to the next. Right now I am using the script found here:
http://mail.zope.org/pipermail/zope-collector-monitor/2003-May/002001.ht
ml
Except I changed,
<dtml-let batch="_.range(100, 180)" batch_size="10" batch_start="REQUEST.get('batch_start',1)">
To
<dtml-let batch="myZSQLMethod1" batch_size="10" batch_start="REQUEST.get('batch_start',1)">
The mySQLMethod1 takes two params which the search form supplies to REQUEST. This works great. The pagination works beautifully. However, when I use the very same result script with myZSQLMethod2 (same DB table), which takes 5 params (all optional) the pagination breaks and no-longer passes the query terms. I have checked and rechecked both scripts and both forms. The ZSQLMethods both test good. I am out of ideas. For the life of me I cannot figure out why I'm losing my query terms in one and not the other when the two are almost identical. Care to enlighten me with your collective wisdom?
In similar situations I have done the following: 1) call a python script/external method which: (i) does the db search; (ii) formats the results as required for display; (iii) returns a tuple that contains: list of search results, url parameters for 'previous' link; url parameters for 'next' link; url parameters for 'first link'; url parameters for 'last' link 2) use a dtml method to call the script/ext.method like <dtml-let rStat="mySearchRoutine(parm1, parm1, ...)"> <dtml-in "rStat[0]"> display code here eg. <dtml-var sequence-item><br> or could be an html/css table, etc. <dtml-if sequence-end> <a href="...?<dtml-var "rStat[1]">">previous</a> <a href="...?<dtml-var "rStat[2]">">next</a> <a href="...?<dtml-var "rStat[3]">">first</a> <a href="...?<dtml-var "rStat[4]">">last</a> </dtml-if> </dtml-in> </dtml-let> This greatly simplifies the dtml and facilitates debugging and future modifications. hth Jonathan
I just use Adobe Labs Spry Framework... this effectively puts the paging in javascript. On 5/31/07, Programmer <programmer@paradigm-corp.com> wrote:
Hi Jonathan,
I have something similar to your idea already. The python script supplies page number to a stored procedure which handles the actual paging. The script takes the result from the proc and builds an html table and handles column sorting on the table. The output of the script is just a single variable so I can just use &dtml-var instead of the flaky &dtml-in. Problem I have now is this new search interface makes use of full-text searching on SQL Server 2K. The paging proc wasn't written to handle it and will need to be rewritten from scratch. This will take a lot of time and testing. I thought I could slap something simple and fast together to use in the interim to allow people to start testing the search engine.
I really do wish Zope would either fix or eliminate broken features. At the very least have the curtesy to say "hey y'all, this is broke, don't bother" so folks don't waste time with it.
Mike
-----Original Message----- From: Jonathan [mailto:dev101@magma.ca] Sent: Wednesday, May 30, 2007 5:22 PM To: Programmer; zope@zope.org Subject: Re: [Zope] a batch of inSaNitY!
----- Original Message ----- From: "Programmer" <programmer@paradigm-corp.com> To: <zope@zope.org> Sent: Wednesday, May 30, 2007 4:44 PM Subject: [Zope] a batch of inSaNitY!
Hi
I am about to go stark, raving, frothing mad with the DTML-IN batching. Is there a known (or unknown) bug with this?
I have searched and read everything I can find about this and no luck. The problem is with carrying the query terms over from one batch page to the next. Right now I am using the script found here:
http://mail.zope.org/pipermail/zope-collector-monitor/2003-May/002001.ht
ml
Except I changed,
<dtml-let batch="_.range(100, 180)" batch_size="10" batch_start="REQUEST.get('batch_start',1)">
To
<dtml-let batch="myZSQLMethod1" batch_size="10" batch_start="REQUEST.get('batch_start',1)">
The mySQLMethod1 takes two params which the search form supplies to REQUEST. This works great. The pagination works beautifully. However, when I use the very same result script with myZSQLMethod2 (same DB table), which takes 5 params (all optional) the pagination breaks and no-longer passes the query terms. I have checked and rechecked both scripts and both forms. The ZSQLMethods both test good. I am out of ideas. For the life of me I cannot figure out why I'm losing my query terms in one and not the other when the two are almost identical. Care to enlighten me with your collective wisdom?
In similar situations I have done the following:
1) call a python script/external method which: (i) does the db search; (ii) formats the results as required for display; (iii) returns a tuple that contains: list of search results, url parameters for 'previous' link; url parameters for 'next' link; url parameters for 'first link'; url parameters for 'last' link
2) use a dtml method to call the script/ext.method like
<dtml-let rStat="mySearchRoutine(parm1, parm1, ...)">
<dtml-in "rStat[0]"> display code here eg. <dtml-var sequence-item><br> or could be an html/css table, etc.
<dtml-if sequence-end> <a href="...?<dtml-var "rStat[1]">">previous</a> <a href="...?<dtml-var "rStat[2]">">next</a> <a href="...?<dtml-var "rStat[3]">">first</a> <a href="...?<dtml-var "rStat[4]">">last</a> </dtml-if>
</dtml-in> </dtml-let>
This greatly simplifies the dtml and facilitates debugging and future modifications.
hth
Jonathan
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
-- Thanks, Derek Wilson
You know I had considered using JS for dealing with this. It does make it much easier to change the CSS on your links to indicate current page and such. I might look into this again. Thanks! ________________________________ From: zope-bounces+programmer=paradigm-corp.com@zope.org [mailto:zope-bounces+programmer=paradigm-corp.com@zope.org] On Behalf Of SpiderX Sent: Thursday, May 31, 2007 11:25 AM To: zope@zope.org Subject: Re: [Zope] a batch of inSaNitY! I just use Adobe Labs Spry Framework... this effectively puts the paging in javascript. On 5/31/07, Programmer < programmer@paradigm-corp.com <mailto:programmer@paradigm-corp.com> > wrote: Hi Jonathan, I have something similar to your idea already. The python script supplies page number to a stored procedure which handles the actual paging. The script takes the result from the proc and builds an html table and handles column sorting on the table. The output of the script is just a single variable so I can just use &dtml-var instead of the flaky &dtml-in. Problem I have now is this new search interface makes use of full-text searching on SQL Server 2K. The paging proc wasn't written to handle it and will need to be rewritten from scratch. This will take a lot of time and testing. I thought I could slap something simple and fast together to use in the interim to allow people to start testing the search engine. I really do wish Zope would either fix or eliminate broken features. At the very least have the curtesy to say "hey y'all, this is broke, don't bother" so folks don't waste time with it. Mike -----Original Message----- From: Jonathan [mailto:dev101@magma.ca] Sent: Wednesday, May 30, 2007 5:22 PM To: Programmer; zope@zope.org Subject: Re: [Zope] a batch of inSaNitY! ----- Original Message ----- From: "Programmer" <programmer@paradigm-corp.com> To: < zope@zope.org <mailto:zope@zope.org> > Sent: Wednesday, May 30, 2007 4:44 PM Subject: [Zope] a batch of inSaNitY! > Hi > > I am about to go stark, raving, frothing mad with the DTML-IN batching. > Is there a known (or unknown) bug with this? > > I have searched and read everything I can find about this and no luck. > The problem is with carrying the query terms over from one batch page to > the next. Right now I am using the script found here: > http://mail.zope.org/pipermail/zope-collector-monitor/2003-May/002001.ht > ml > > Except I changed, > > <dtml-let > batch="_.range(100, 180)" > batch_size="10" > batch_start="REQUEST.get('batch_start',1)"> > > To > > <dtml-let > batch="myZSQLMethod1" > batch_size="10" > batch_start="REQUEST.get('batch_start',1)"> > > The mySQLMethod1 takes two params which the search form supplies to > REQUEST. This works great. The pagination works beautifully. However, > when I use the very same result script with myZSQLMethod2 (same DB > table), which takes 5 params (all optional) the pagination breaks and > no-longer passes the query terms. > I have checked and rechecked both scripts and both forms. The > ZSQLMethods both test good. I am out of ideas. For the life of me I > cannot figure out why I'm losing my query terms in one and not the other > when the two are almost identical. > Care to enlighten me with your collective wisdom? In similar situations I have done the following: 1) call a python script/external method which: (i) does the db search; (ii) formats the results as required for display; (iii) returns a tuple that contains: list of search results, url parameters for 'previous' link; url parameters for 'next' link; url parameters for 'first link'; url parameters for 'last' link 2) use a dtml method to call the script/ext.method like <dtml-let rStat="mySearchRoutine(parm1, parm1, ...)"> <dtml-in "rStat[0]"> display code here eg. <dtml-var sequence-item><br> or could be an html/css table, etc. <dtml-if sequence-end> <a href="...?<dtml-var "rStat[1]">">previous</a> <a href="...?<dtml-var "rStat[2]">">next</a> <a href="...?<dtml-var "rStat[3]">">first</a> <a href="...?<dtml-var "rStat[4]">">last</a> </dtml-if> </dtml-in> </dtml-let> This greatly simplifies the dtml and facilitates debugging and future modifications. hth Jonathan _______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev ) -- Thanks, Derek Wilson
I'm considering upgrading from Zope 2.9.0 to 2.9.7. Has anyone done this before that can offer advice? Any tips? I'm on Win32. I have custom products installed, custom development, etc etc... can I just run the Installer for 2.9.7 and it will upgrade automatically?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 6 Jun 2007, at 21:14, SpiderX wrote:
I'm considering upgrading from Zope 2.9.0 to 2.9.7. Has anyone done this before that can offer advice? Any tips? I'm on Win32. I have custom products installed, custom development, etc etc... can I just run the Installer for 2.9.7 and it will upgrade automatically?
Your safest bet is to recreate that setup on a second box and run the upgrade there to see if there are any problems. If there aren't, run it on your original installation. jens -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFGZ8ubRAx5nvEhZLIRAoakAJ9u7LRhkQwab5l9JYfCReTlOCwP3gCfZHF0 fLGM2t2YxpjyOeF/eCDI/3A= =1bD5 -----END PGP SIGNATURE-----
This is curious... The problem I had with the searchterms not getting carried across pages seems to have gone away. Here's what I changed. The two search forms are separate dtml-methods and still are but I've included them into the main page template like I originally planned. Something like this: <html> <body> <div> <dtml-var form1> </div> <div> <dtml-var form2> </div> <etc. etc. When the template is rendered both forms are rendered also. Except now nothing breaks. The result page dtml scripts are still the same. I'm scratching my head... At least people can test the search facility while a more permanent python + AJAX interfaces are built.
participants (4)
-
Jens Vagelpohl -
Jonathan -
Programmer -
SpiderX