hi chris,
right. if i run 'psql -d soma' and then type the first SELECT, i get
results ... if i type the second SELECT, i get zero rows. this seemed
odd to me ... i wouldn't think that postgres would care. but perhaps it
does
hmm. ok, i just tried this again ... and now i'm getting results, no
matter whether i include single quotes or not, in the syntax of the SELECT
and ... now i'm getting the same results, from both the psql interface
*and* from my php interface
so. where does this leave me. was i hallucinating a few days ago? i
find that hard to believe -- i spent a couple hours building that post,
along with all the supporting traces
ok, if this effect were continuing ... where the single quotes mattered
... what would that lead you to suggest? some issue inside PostGres itself?
--sk
^M's are newlines, nothing to worry about.
So if you do the same query with & without the quotes it behaves
differently?
SELECT mac, ip_addr, vlan, ad_ou, current_os_user, os_hostname,
dns_hostname, version_name, snmp_sys_descr, snmp_sys_objectid,
first_seen, last_seen, last_updated FROM hosts LEFT JOIN os_versions ON
hosts.osver = os_versions.versionid WHERE last_seen > 2006-08-14 AND
vlan = 74 ORDER BY ip_addr ASC;
vs
SELECT mac, ip_addr, vlan, ad_ou, current_os_user, os_hostname,
dns_hostname, version_name, snmp_sys_descr, snmp_sys_objectid,
first_seen, last_seen, last_updated FROM hosts LEFT JOIN os_versions ON
hosts.osver = os_versions.versionid WHERE last_seen > '2006-08-14' AND
vlan = '74' ORDER BY ip_addr ASC;
--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
