|
|
Posted by Steve on 11/07/07 21:37
"Darko" <darko.maksimovic@gmail.com> wrote in message
news:1194463439.305946.20240@z9g2000hsf.googlegroups.com...
> On Nov 7, 6:19 pm, "Steve" <no....@example.com> wrote:
>> well !!! lo-and-behold!!! when you get your error message back THIS time,
>> you actually get a line number OTHER THAN 1 !!! now THAT would be
>> helpful!
>> imagine too, that you echo this out to the browser, copy it, and paste it
>> directly into your mysql query browser...then execute it. even before
>> then,
>> you might have discovered (since you can now READ IT) that there is
>> something wrong in the data you're inserting.
>>
>
> Having yelled that out, haven't you ever noticed that mysql (and so do
> other
> sql servers) specify precisely where the problem is - this time it
> said:
>
>> near 'from, size, format, cat, host ...
you obviously haven't written very long or complex queries. 'near' and ON
LINE x are *worlds* apart, now aren't they.
> ... so it was quite clear that it had had problem with "from".
apparently not quite as clear to the op. :)
> Considering php and
> queries code readability you are, of course, right, since a programmer
> will much more
> easily read the code formatted in the way you have, but considering
> error information,
you should ammend that...'considering the error information [IN THIS CASE]'.
either way, it should be formatted as a rule...unless you're saying you can
predict your errors, in which case you wouldn't make mistakes anyway.
> sql servers are pretty precise about where the problem occurred, code
> being indented
> or not.
really? which ones? what is 'pretty' precise?
the indenting is multipurpose. it is my experience that the top 4 sql
servers (ms sql, oracle, mysql, teradata) are generally *obtuse* in their
error messages...but they all give line numbers!
>> don't let me throw you on that one...bad data is NOT the problem here.
>> there
>> are things called RESERVED WORDS. one of those would be the word
>> 'FROM'...as
>> in "select * FROM". if you had correctly formatted your sql statement,
>> the
>> line number in error would have been line 6...a much better clue.
>
> As for rude yelling about making mistakes with reserved words, that is
> something that happens
> to many people, even experienced, from time to time, so no need to get
> upset about it.
rude? lol.
you even infer rudeness about the mistake itself. no, i capitalized FROM so
that it stood out. if that hurt your ears, then you won't hear me laughing
right now. my intention throughout the thread here has been to make a point
about formatting. did you not notice that even though i told him what the
problem was, i did not tell him how to fix it? hmmmm...must not have been
the goal of my post. seems you've missed that point.
> I once
> named two variables in C like "od" and "do", and couldn't find out
> what was wrong with it until
> I realised it was the "do" keyword.
christ almighty! i suppose you proliferate the use of variables like $tmp
too. what a goof! 'do'? for the love of god, almost *every* language has a
*do* loop construct. so, when you said, 'even experienced' above, you were
not associating yourself among those. :)
> Finally, it is not "reserved" word in any sql, as you can indeed name
> any field "from", as long
> as you make the parser know it. For an example, this is totally legal:
>
> select name, img, descr, "from", size, format from table;
why yes. now why would i NOT explain that to the op? must not have been the
purpose of my post. what's more, i'd be encouraging BAD behavior. if you
think that's just my ho, why don't you prepose that question in a db
forum...bring your asbestos umbrella, cuz it'll rain fire from the first
response to the last. dba's are kinda picky that way.
> just as long as you keep the double quotes around key words.
ahhhh...you assume too much. oracle will fart on your double quotes. it
likes either single tics or single back tics (`). again, you just killed a
great chance for scalability. you should be able to take your code base and
plop it down in front of any db and nothing breaks. you've forced yourself
to reprogram when switching from one db to another...which is the shits when
you're prototyping on your local pc using mysql and pushing code to
production where teradata is the db being used.
wanna keep going, darko?
Navigation:
[Reply to this message]
|