--- Chris Withers <chris@simplistix.co.uk> wrote:

...

I used the following and it works great (without some formatting for clarity): <tr tal:define="customer container/getCustomerLicences" tal:condition="customer"> <td>Customer: <span tal:content="python:customer[0]['full_name']"></span></td> </tr>

hmm, this strikes me as just plain wrong :-S

Why is getCustomerLicenses returning more than one row if you only want the first one?

In my original post I mentioned that getCustomerLicenses returns more than one row and I want to create something of a header.

If it only returned one row, then you could do:

<tr tal:repeat="customer container/getCustomerLicences"> <td> Customer: <span tal:content="customer/full_name"></span> </td> </tr>

...no need for the condition or the yucky integer indexes.

True.

Now, if you really can't stop your sql returning more than one row (LIMIT 1 anyone?) then how about:

<tr tal:define="customers container/getCustomerLicences; customer python:customers and customers[0]" tal:condition="customer"> <td> Customer: <span tal:content="customer/full_name"></span> </td> </tr>

To have my SQL returning only just 1 row would require another Z SQL Method, in which case it may as well be something like getCustomer. I'm still getting my head around TAL and how it works so I'm not sure how the "python:customers and customers[0]" code works. Ideally, I want to use just the one Z SQL method (done) but I guess it would be better coding to just reference the Z SQL method once. Currently the page template makes two calls to the Z SQL method. Once for the customer header and another to retrieve the customer license details. Can you suggest how this would be done? I'm also thinking further along the lines too of a page template, printing all customers with headers and details for each. This would use a SQL "GROUP BY" statement. .. But this is still out of my scope of knowledge. Regards, Julian

--- Tino Wildenhain <tino@wildenhain.de> wrote:

Am Mittwoch, den 28.09.2005, 16:32 +1000 schrieb Julian Yap:

...

--- Chris Withers <chris@simplistix.co.uk> wrote: ...

...

Now, if you really can't stop your sql returning more than one row (LIMIT 1 anyone?) then how about:

<tr tal:define="customers container/getCustomerLicences; customer python:customers and customers[0]" tal:condition="customer"> <td> Customer: <span tal:content="customer/full_name"></span> </td> </tr>

To have my SQL returning only just 1 row would require another Z SQL Method, in which case it may as well be something like getCustomer.

I'm still getting my head around TAL and how it works so I'm not sure how the "python:customers and customers[0]" code works.

Ideally, I want to use just the one Z SQL method (done) but I guess it would be better coding to just reference the Z SQL method once. Currently the page template makes two calls to the Z SQL method. Once for the customer header and another to retrieve the customer license details. Can you suggest how this would be done?

You could just wrap it in a simple python script:

results=context.yourZSQLMethod()

h=results[:1] # see python slice b=results[1:]

return context.yourPageTemplate(header=h,body=b)

And in your ZPT use tal:repeat="chead options/header" and options/body

But maybe you can rething and rephrase your problem :-)

Thanks Tino. Your example of using the Python script really opens my eyes to how everything fits together (I know Python). I'm not sure about the TAL statement you used (so what else is new). ... OK, I just got back from reading about the "options" keyword in Page Templates... Very useful. Thanks for the usage Python tip. I think that will get me going for a while. Another query I had was on the practice of using control flow (ie. if, for, etc.. statements). I guess the best way is to keep your control flow in Python scripts? Is this the common practise?