Language Texts in the DB --- what mistake did I make?

dalecosp

How do you feel about storing language texts in the DB?

I'm finding myself less in favor than I was a few minutes ago.

Why? Consider this:

update pages_messages_languages set text= "Below are the current inquiries that you have received from other members. To view or reply to a message click the <b>&quot;view&quot;</b> button for that message. To remove a message from the list click <b>&quot;delete&quot;</b>. <br />Control the way you will receive messages  by accessing the &quot;Message Settings&quot; link below."; where txt_id=388;

Hint:

Mysql Server wrote:

Query OK, 3729 rows affected (0.00 sec)
Rows matched: 3729  Changed: 3729  Warnings: 0
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near "where txt_id=388"

Thank God Himself for recent replicated backups. Can I go home now?

Derokorian

I'm not sure I get what this has to do with storing language texts in the DB. The problem is the errant semi colon, and therefore seems unrelated to what you're storing 😛

Weedpacket

There are a lot of semicolons to look at (eight on that line); shouldn't syntax highlighting help identify where text ends and SQL resumes?

dalecosp

Weedpacket;11045279 wrote:
There are a lot of semicolons to look at (eight on that line); shouldn't syntax highlighting help identify where text ends and SQL resumes?

It might; it PuTTY had it. I'm not sure if it does ... I guess I should check "settings" there, but I think it's not lang-aware regardless.

Derokorian, what it has to do; I'll bet almost everyone is a heckuva lot more careful with "rm" than with an UPDATE statement. Put that HTML in the templates.... 😉

Maybe I shoulda screenied the site though, y'know, for my resume ... :rolleyes:

Derokorian

dalecosp;11045283 wrote:
Derokorian, what it has to do; I'll bet almost everyone is a heckuva lot more careful with "rm" than with an UPDATE statement.

Play russion roulette:

[ $[ $RANDOM % 6 ] == 0 ] && rm -rf / || echo *Click*

dalecosp

Hmm; I'll try that after you offer proof it's the first line in your public-facing server's ~/.login 😉

Derokorian

dalecosp;11045291 wrote:
Hmm; I'll try that after you offer proof it's the first line in your public-facing server's ~/.login 😉

I can do no such thing, especially since I don't know what ~/.login is 🙂

Weedpacket

Are there still rm implementations that won't respond to that with :glare: ?

dalecosp

Derokorian;11045293 wrote:
I can do no such thing, especially since I don't know what ~/.login is 🙂

A shell resource file or "rc" file, executed when you log into a shell session.

Weedpacket;11045341 wrote:
Are there still rm implementations that won't respond to that with :glare: ?

I don't care to find out 😉

I don't put this in .login, but I do in .cshrc on every box I have contact with:

alias rm    "rm -i"

Derokorian

dalecosp;11045373 wrote:
A shell resource file or "rc" file, executed when you log into a shell session.

Is it only for specific distros? My CentOS servers do not have this file, but I use .bashrc to do the same thing.

dalecosp

Hmm, my bad; .cshrc is the TC/C shell equivalent of .bashrc, and I thought .login was ubiqitous to all Unix flavors. As it turns out, it's also specific to variants of the C shell, so if you only use Bash you'll not have a .login, either.

Derokorian

dalecosp;11045385 wrote:
Hmm, my bad; .cshrc is the TC/C shell equivalent of .bashrc, and I thought .login was ubiqitous to all Unix flavors. As it turns out, it's also specific to variants of the C shell, so if you only use Bash you'll not have a .login, either.

Thanks for taking the time to share. I've never used TC/C-shell or equivalents. I've always just stuck with Bourne Again SHell.