Adding TABLE_PREFIX in a manual query

[Mr Blunt]

Thanks for moving thread, and again I apolize for that .... rookie move, LOL.
And interesting sidenotes guys!!
Learn sumptin new everyday.

So Christine answered my last question and I'll remove the semicolon from future readme's, but unfortunately since I've written a public file that had one, and since I'm still learning, can I get further clarification as I could have been more specific.

Can the use of a semicolon at line end of a manual query cause a problem?
..... like for people who previously ran it that way.

[akanevsky]

If you want to be compatible with every system/configuration, you should stick to ANSI SQL, and use ADD COLUMN. There are no garantuees that i would work in future versions, and if vB would sometime support other database system (Oracle for example), you would be in more problems with only a ADD.

Oh... I understand, thanks for the explanation

[Marco van Herwaarden]

Originally Posted by Mr Blunt

Thanks for moving thread, and again I apolize for that .... rookie move, LOL.
And interesting sidenotes guys!!
Learn sumptin new everyday.

So Christine answered my last question and I'll remove the semicolon from future readme's, but unfortunately since I've written a public file that had one, and since I'm still learning, can I get further clarification as I could have been more specific.

Can the use of a semicolon at line end of a manual query cause a problem?
..... like for people who previously ran it that way.

About the semi-colon, it is the same story. According to the SQL-standards a command is ended by a semi-colon. In my opinion you should always add it. The AdminCP will automatic add (actually the SQL-routines) one of you ommit it.

[Mr Blunt]

Thanks again!!
I love definative answers!!