I think it does. Thank you so much!
GJ
--
View this message in context:
http://zend-framework-community.634137.n4.nabble.com/Pls-help-with-unwanted-quotes-in-db-queries-tp4659783p4659793.html
Sent from the Zend Framework mailing list archive at Nabble.com.
--
List: fw-general@lists.zend.com
Hi,
So the deal here (in my case): if I want to join on numeric columns (and
that are datatyped as such in mysql), the conversion doesn't take that much
time in small tables; however, in large ones, it will add up.
It's just that I don't know the reasoning behind the omission of this
feature go
Well, it might be a misconception on my part; however there's this in the
mysql docs:
https://dev.mysql.com/doc/refman/5.5/en/optimize-numeric.html
and there's this thread on stackoverflow:
http://stackoverflow.com/questions/4918512/disadvantages-of-quoting-integers-in-a-mysql-query
So the deal h
is, I think, much slower than
"select * from xyz where id=534",
especially if the id is datatyped as int in Mysql, and even more so when
there is an index on that column.
Where does mysql document this performance optimization? Everything I
see says this is a micro-optimization at best.
Thank you, I will look into those examples.
ralphschindler wrote
>> And on a related issue: In Zf1 you were able to provide a data-type with
>> any
>> query-part, so you were able to actually use optimal data-types for your
>> database (i.e. an int was treated as int). Now even an int gets quoted