Home/ Questions/Q 6118623
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T15:27:30+00:00

What’s the best route for storing data in MySQL. With MySQL should I just

  • 0

What’s the best route for storing data in MySQL. With MySQL should I just use, TEXT as my field type?

As well when using mysql_real_escape_string() with return’ed values \r\n .
But should I be running the htmlentities() on it after that?

And then when I return data to the screen I should use, NL2BR()?

Just trying to figure out the best route here for storing this information.

Thank you for your help!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    TEXT or TINYTEXT or anything similar should be fine for storing ASCII data from the user. If you don’t need a lot of space you may think about VARCHAR

    i think that mysql_real_escape_string() escapes characters that may compromise the security of an SQL query (single quote, double quote, etc.) but doesn’t do much more than that.

    htmlentities() converts reserved html characters like < and > into their html encoded equivalent, &lt; and &gt; respectively. These characters are not dangerous for SQL queries so you probably do not need to escape them unless you want to display the HTML tag entered by the user as text, and not let it be interpreted as HTML.

    NL2BR() is probably not necessary either.

    Most importantly, your decision on when to use each of these functions will depend on your end application. You may need / want some but not others ( though you should definitely use mysql_real_escape_string() )

    • 0