Re: Using q() to define a query
- From: cww@xxxxxxxxxxxxxxxx (Colin Wetherbee)
- Date: Fri, 11 Jan 2008 11:00:41 -0500
Jonathan Leffler wrote:
On Jan 10, 2008 7:59 PM, Colin Wetherbee <cww@xxxxxxxxxxxxxxxx <mailto:cww@xxxxxxxxxxxxxxxx>> wrote:
[Fri Jan 11 03:49:09 2008] [debug] Log.pm(36): [client
192.168.171.80 <http://192.168.171.80>]
[JetSet] SELECT departure_date, eq.name <http://eq.name> AS
equipment,\n
dp.full_city AS departure_city, ap.full_city AS arrival_city,\n
ca.name <http://ca.name> AS carrier_name, number\n FROM
jsjourneys\n FULL OUTER
JOIN jscarriers AS ca ON jsjourneys.carrier = ca.id\n FULL OUTER
JOIN jsequipment AS eq ON jsjourneys.equipment = eq.id\n JOIN
jsports AS dp ON jsjourneys.departure_port = dp.id\n JOIN jsports
AS ap ON jsjourneys.arrival_port = ap.id\n ORDER BY departure_date
Notice the newline characters in there. If those were really in the
query, I can't imagine the database would run it, so I suppose they're
an artifact of the combination of using q() to quote my query and using
Apache's logger to output it.
If you're referring to the newlines in the $sql string - I'd be astonished if the DBMS did not handle them OK. If you're referring to the \n notation in the log output, I'd assume those are interpolated by the Apache logging module.
I'm somewhat surprised Apache didn't parse the newlines, though... which made me wonder whether they were showing up as literal '\n' in the query, too? Probably not.
Colin
.
- References:
- Using q() to define a query
- From: Colin Wetherbee
- Re: Using q() to define a query
- From: Jonathan Leffler
- Using q() to define a query
- Prev by Date: Re: Using q() to define a query
- Next by Date: RE: Using q() to define a query
- Previous by thread: Re: Using q() to define a query
- Next by thread: Re: Using q() to define a query
- Index(es):
Relevant Pages
|
