Shekar,
actually the documentation does not mention this usage.
And there are also no testcases.
All testcases have approved before I did my commit.
Actually, giving an array as input would result in each single placeholder
to be replaced.
where(price ? and price = ?, array(2, 10));
Shekar,
to get my snippet working with previous versions you would just have to add
a version check...
if (Zend_Version::compareVersions('1.0.2') 0) {
// change where
}
or you wait for the issue to be solved...
1.0.4 I think as in 4 days the new release comes out.
Greetings
Thomas
I18N
Hi Terry,
My apologies for the late reply... I ran into this issue with PDO as
well. I was able to work around it by using the PDO ODBC adapter, where
only the DSN is required. IIRC, I got NT Authentication to work like
that, however, I haven't actually done this since shortly after PHP 5
I guess the new method should be named inWhere().
On 11/21/07, Shekar C Reddy [EMAIL PROTECTED] wrote:
Thomas,
I encourage you to test the where() method with v1.0.2 and see the results
- it generates SQL imploding all the array values into a single placeholder
as expected. The
Please ignore the new suggested name. It is a part of the where clause
[where()/orWhere()] and so, in() would be ideal:
$select-where($select-in( ... ));
$select-orWhere( $select-in( ... ));
Thanks
On 11/21/07, Shekar C Reddy [EMAIL PROTECTED] wrote:
I guess the new method should be
This is wrong...
Actually I made a PDO ODBC Adapter.
You can find it within the incubator.
Greetings
Thomas
I18N Team Leader
- Original Message -
From: Bryce Lohr [EMAIL PROTECTED]
To: Terry Shipclark [EMAIL PROTECTED]; fw-general@lists.zend.com
Sent: Wednesday, November 21, 2007
Thomas,
Don't take this the wrong way but these casual massive changes to the way
existing code works is the reason why I stopped using Zend_Db back in the .8
days. By taking away the array imploding functionality you have just broken
a considerable amount of existing code. Code written in
Art,
as I said in past we reviewed what was written within the documentation and
within the testbed.
The usecases did not brake anyone of the behaviour mentioned there.
Then we looked over the opened issues and discussed about the additional
usecases we want to support.
This mentioned
Before I dive into it, I'll admit to being a bit weak in the whole
request/response flow, so bear with me if this is slightly obtuse.
I've got an account creation page that works through one module. After
account creation, I want to forward that user to my Auth controller, login
action, which
I think the only way to do this would be to create an HTML page with a form
and some javascript that would perform a submit() when the page loads. This
is dangerous though because you would have to embed the username/password or
some sort of key/hash as a hidden form field.
On Nov 21, 2007 8:59
Hi
If you simply forward (/$this-_forward()/), then all the POST-data
remains. A redirect (/$this-_redirect()/ or per redirector-helper) is a
new request made by the browser and regulary there is no way to perform
such a redirect with POST-data, but i dont see any cause to do this. You
are
Zend 0.8.0 had the use of where IN (?) array documented. As well as previous
versions.
Zend 0.9.0 did not have it documented
Zend 0.9.1 was the first release with Zend_Db_Select unit test cases and, as
you say, did not have an array test or any tests with multiple ? place
holders
Zend 1.0.2
Does this require any changes to the php installation. Although I do believe
that I may have enough pull to get pdo odbc support added to the server, this
may take some time.
I am not at a computer right now, however if I recall correctly odbc wasn't
listed as one of the pdo drivers
I made this PDO ODBC Adapter because I had to connect to MSDE on a Win2000
Machine.
I ran it successfully with systemdsn and unconfigured Msde connections with
success.
Of course I can not guarantee that all things are working, but that's the
reason why it's still in the incubator.
It
Thank you for the clarification on this, Thomas. I was unaware of your
adapter in the incubator.
Regards,
Bryce Lohr
Thomas Weidner wrote:
This is wrong...
Actually I made a PDO ODBC Adapter.
You can find it within the incubator.
Greetings
Thomas
I18N Team Leader
- Original Message
Since ZF 1.0 was released the Prime Directive is to preserve backward
compatibility if possible. This includes when resolving reported bugs or
feature requests; the behavior of ZF 1.0 must be preserved for Zend
Framework's mission to be accomplished.
I understand that it is tempting to change
Hello! I'm constantly running in to these types of issues. I must be doing
something fundamentally wrong. I've instantiated a database connection like
so:
// --
$dsn = $config-dbadaptor . :// // Build a DSN string
DB::connect looks like a PEAR factory method - are you sure you're
using Zend Framework? If not, you'd need to post to a PEAR mailing list.
Hello! I'm constantly running in to these types of issues. I must be
doing something fundamentally wrong. I've instantiated a database
connection
Unit tests where not lacking...
I added docu and unit tests to all my changes. I ran all unit tests before I
did my commit.
And how should I receive backwards compatibility if there are no tests and
no documentation so people did not know that this even exists ?
It's impossible because there
Woops! Ha ha ha. I'm an idiot. Sorry about that. I got confused about
which database library I was using. Thanks!
Simon Mundy wrote:
DB::connect looks like a PEAR factory method - are you sure you're
using Zend Framework? If not, you'd need to post to a PEAR mailing list.
Hello!
Hi Thomas
In fairness I also didn't know of that usecase - however there is a
similar usage in Zend_Db_Table::find(). So it would seem to hold that
where one would exist the other would behave similarly - and since Art
and Shekar have indicated that it did exist in that form I have no
Hi Thomas, Bill, all
I've just had another thought...
Currently the API allows for immediate substitution - the ? takes the
value of the second parameter and it is quoted before being added to
the select object.
Perhaps it should stay that way?
For the new functionality suggested by
22 matches
Mail list logo
