MySQL table names in PHP code

[MikeB]

I'm learning PHP and MySQL. In the samples I work with, the SQL table
names are "escaped" in accent grave (`) marks, not in single or double
quotes.

Can anyone explain that?

For instance, I have the following:

$sql_command = "SELECT * from `7-1_List`";

I tried looking around on the php.net site, but clearly I'm not using
the right search terms.

While I'm asking, I think I've figured out how double quotes (")
differ from single quotes ('), but if there is a discussion that
someone can point me to, that would be very nice.

Thanks.

[Guillaume]

Jerry Stuckle a écrit :

Yes and no. His question was about the backticks. A side comment
related to him having single vs. double quotes figured out (he thinks).

Whatever, just quit it, who cares actually ?
At least the comment you consider as inappropriate is the most PHP
oriented of this topic. Not such a big deal.

Regards,
--
Guillaume

[Jerry Stuckle]

Guillaume wrote:

Jerry Stuckle a écrit :

>Yes and no. His question was about the backticks. A side comment
related to him having single vs. double quotes figured out (he thinks).

Whatever, just quit it, who cares actually ?
At least the comment you consider as inappropriate is the most PHP
oriented of this topic. Not such a big deal.

Regards,

No, backticks in MySQL table names has nothing to do with PHP. They're
not used by other databases, but the syntax is identical in other
languages when calling MySQL.

It has nothing to do with PHP - which is why it is not documented in the
PHP manual (but it is in the MySQL manual - which should give you a hint).

--
=============== ===
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attgl obal.net
=============== ===

[Guillaume]

>the comment you consider as inappropriate
I was talking about Chuck's comment, which only concern was quotes vs
double quotes in PHP. Which indeed was the nearest to the NG subject,
though it may (or may not) be appropriate to the OP.

I mean, he would have said something not really exact, appropriate or
accurate, if OT then one could say "don't post if that's OT and possibly
useless".
While Chuck posted something that *may* be useless to the OP (depends on
what he really meant), but at least is related to the topic.

Regards,
--
Guillaume

[MikeB]

Wow. OK, firstly thank you all for the polite way you answered my
first question while pointing out that it was also OT. Other forums
are not always so kind.

Since I didn't realize that the backticks were SQL, I guess I
conflated them with quotes and double quotes to some extent.

I did actually ask two questions, the first one about the backticks
and then a secondary and much less important question about the quotes
vs double quotes issue so that I could read up on those and make sure
my understanding of them were thorough.

So I appreciate the responses I got to both answers. Thank you all.