Databases
StackOverflow2013
Postsdbo
POWhat may cause question marks instead of non-ASCII symbols?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhat may cause question marks instead of non-ASCII symbols?
    primarykey
    data
    text
    <p>Can't figure out why is it happening, there is definitely something wrong with the enviroment. I have db declared as</p> <pre><code>CREATE DATABASE `mydb` /*!40100 DEFAULT CHARACTER SET latin1 */ </code></pre> <p>Then I have a table declared as </p> <pre><code>CREATE TABLE `myabstract_table` ( `key_id` int(10) unsigned NOT NULL AUTO_INCREMENT, `varchar_field` varchar(128) NOT NULL PRIMARY KEY (`key_id`) ) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8; </code></pre> <p>Then I have usual for this case php code:</p> <pre><code>function execSQL($conn, $sql, $values = false) { try { $stmt = $conn-&gt;prepare($sql); if ($values) foreach($values as $param=&gt;$value) $stmt-&gt;bindValue($param, $value); if ( ! $stmt-&gt;execute() ) { error_log ("PDO Error: ".json_encode($stmt-&gt;errorInfo())); return false; } } catch (PDOException $e) { error_log ("Exception: " . $e-&gt;getMessage()); return false; } return $stmt; } </code></pre> <p>and after that the strings are saving (via INSERT statement) to db with <strong>question marks</strong> instead of non-ASCII symbols</p> <p>PS. I perform <code>set names 'utf8'</code> before any sql request, all php stuff is cofigured for UTF-8, html document header contains meta tag with UTF-8 secified as charset; the only thing I didn't try is to change default charset of schema itself (it's currently latin1) since I'm pretty sure it's not at issue. Or is it?</p> <p><img src="https://i.stack.imgur.com/8fJFt.png" alt="enter image description here"></p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USheximal
    1. USheximal
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhat may cause question marks instead of non-ASCII symbols?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWhat may cause question marks instead of non-ASCII symbols?
      1. This table or related slice is empty.
      1. VTDownMod
    3. VO
      singulars
      1. POWhat may cause question marks instead of non-ASCII symbols?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIts all happening because of collation use `utf8_general_ci` everywhere.
      singulars
      1. POWhat may cause question marks instead of non-ASCII symbols?
      1. USYogesh Suthar
    2. CO@Yogesh Collation is not the same as *encoding*, and he's using `utf8` as encoding already!
      singulars
      1. POWhat may cause question marks instead of non-ASCII symbols?
      1. USdeceze
    3. COIs your data actually encoded in UTF-8? See [Handling Unicode Front To Back In A Web App](http://kunststube.net/frontback/).
      singulars
      1. POWhat may cause question marks instead of non-ASCII symbols?
      1. USdeceze
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload