Could having ^M in a query crash a server?

[spags]

I can't test this right now ..for reasons too complicated to explain. A script had been saved in dos mode so there was ^M at the end of each line...

this sql statement spans multiple lines:

$sql = "SELECT
            empl_key,
            bus_office,
            bus_div
        FROM
           data_employee
        WHERE
            empl_dom = '" . $data['dom] . "'
        AND
            empl_user = '" . $data['user'] . "'
        AND
            empl_active = 1";

$result = $db->query( $sql );

And it appeared to crash at the line. (we are using pear, but I don't think that would matter?) There are many other factors that might cause the server to crash..but we thought maybe this might cause it? anybody know?

[spags]

I think the problem is due to an old version of php Php 4.1.2 that had problems with sessions....

[AstroTeg]

^M is ASCII 13 or hex 0D or in English: a carriage return. That's all it is. Its missing the line feed which usually hangs out with the carriage return (example: 0D0A or ASCII 13 ASCII 10).

I'm not a PHP version expert, but I'd hope PHP doesn't get hung up on just the return.

When working with queries, it can be VERY helpful to output the created query BEFORE running the query against the database. I'd even recommend putting an exit() after the echo and before the $result = $db->query( $sql ) line so you can actually see the query. Is it bombing out when it tries running the query? If so, you might copy the query and put it in phpMyAdmin and see what it does there (does it crash or give you an error?)