-- Guillaume ORIOL go.li...@technema.fr wrote
(on Monday, 04 October 2010, 11:38 AM +0200):
Two special parameters are checked when processing requests in
Zend_Rest_Route:
new and edit (in the match() method).
What is the purpose of those special GET URI's?
I would like to use the new
I agree; iterating over a limit 0 result set should result in no more than
0 iterations. Have you filed a bug report?
--
Hector Virgen
Sent from my Droid X
On Oct 4, 2010 2:17 AM, Daniel Latter dan.lat...@gmail.com wrote:
what i meant was if you do happen to pass a zero to the limit method, then
what i meant was if you do happen to pass a zero to the limit method, then
say loop over the (possibly millions of rows it will return) returned rows,
couldn't this potentially bring down a server?
Daniel.
2010/10/3 Valeriy Yatsko d...@design.ru
Good day
Yes, but it doesnt seem right to
not yet, will do later.
Daniel
On 4 October 2010 15:42, Hector Virgen djvir...@gmail.com wrote:
I agree; iterating over a limit 0 result set should result in no more
than 0 iterations. Have you filed a bug report?
--
Hector Virgen
Sent from my Droid X
On Oct 4, 2010 2:17 AM, Daniel
Two special parameters are checked when processing requests in Zend_Rest_Route:
new and edit (in the match() method).
What is the purpose of those special GET URI's?
I would like to use the new parameter to get the initial state of a resource and try to figure if
it is the right way to do so.
Two special parameters are checked when processing requests in
Zend_Rest_Route:
new and edit (in the match() method).
What is the purpose of those special GET URI's?
I would like to use the new parameter to get the initial state of
a resource and try to figure if it is the right way
There is some more discussion here:
http://framework.zend.com/issues/browse/ZF-7666
I'd follow up on that thread.
The problem is that LIMIT is not an SQL standard, and there is no
standard approach.
http://troels.arvin.dk/db/rdbms/#select-limit
As such, our API in ZF1 needs to remain as
Hi,
ok will do.
But what if a zero did happen to get through? would you put this down to
just bad down to bad code and testing?
PS any news on my Zend/Dom commit for exceptions branch? i did submit
another pull request? I have it working with eclipse now so Ill try again if
now good?
Thanks
Hi All,
Ticket #1 on the bug tracker has added a functionality and was
committed on release r22850.
It changes the having() method in Zend_Db_Select to allow us to pass the
optional third parameter which way the $value should be quoted.
The patch was :
-if (func_num_args() 1)
Has anyone developed a header Content-MD5 module for ZF yet?
Kevin McArthur
10 matches
Mail list logo