postgresql explicit encoding set

Works on 2 live sites!

In database.mysql.inc and database.mysqli.inc

function db_connect($url) {
....
  // Force UTF-8.
  mysql_query('SET NAMES "utf8"', $connection);
  return $connection;
}

So it's required for postgresql!

Thanks, committed to Drupal 6. Is this still applicable to Drupal 7? (If not, please put back to "6.x", "fixed").

Yes I think it does apply to Postgres on D7 as well. It should be a trivial patch for someone to write. See the new MySQL driver for the one-line example. It should be nearly identical.

D7 patch here

What's up? It's so trivial to be erroneus

Hi again, Alex!
Any news on it? Will it be introduced to HEAD?

I'll do some testes and rework soon, cause I also think pgsql is much better than mysql. Table corruptions are so common on my site... :(

+Subscribing

So here re-roll for new DB layer

In [1], two syntaxes are described:

• SET CLIENT_ENCODING TO 'value';
• and the standard SQL form SET NAMES 'value';

I would rather go with the standard form, which we use on MySQL already. Either way, this needs work.

[1] http://www.postgresql.org/docs/8.3/static/multibyte.html

so here is SET NAMES as in Mysql

I'd like the PostgreSQL maintainers (DamZ or fiasco) to approve this.

Make sense to me, thanks @andypost.

Committed to CVS HEAD. Thanks!