@mike orr
$ sudo apt-get install command-not-found
$ mysql_config
The program 'mysql_config' is currently not installed. You can
install it by typing:
apt-get install libmysqlclient15-dev
$ sudo apt-get install libmysqlclient15-dev
or
$ sudo apt-get install apt-file
$ apt-file update
$
On 5/29/07, David Smith [EMAIL PROTECTED] wrote:
There was one point you made that I believe is inaccurate and so did not
include it in the above. Where you said that if you want to use the
convert_unicode option, you must know what encoding the database is in, but
my tests don't suggest
jj, I actually agree strongly with you regarding the potential dangers. My
counter argument is that if you specify the encoding of the database in the
config file to a different encoding than is in the mysql config file, don't
you risk double-encoding anyway? Now that the bug is fixed in MySQLdb,
Hi David,
On 5/29/07, David Smith [EMAIL PROTECTED] wrote:
Max, I have no problems by only using Unicode field-types in my model;
that
is, my sqlalchemy connection string does not contain anything related to
UTF-8. I haven't investigated my MySQL setup so thoroughly but it seems to
work
Hi Max, thanks for the quick response,
Max Ischenko wrote:
My exprience shows that it may be necessarily to specify encoding for
mysql in dburi.
The reason is that mysql server may be configured with default encoding
that doesn't match the database you're connecting to. E.g. if you open
On 5/29/07, David Smith [EMAIL PROTECTED] wrote:
jj, I actually agree strongly with you regarding the potential dangers. My
counter argument is that if you specify the encoding of the database in the
config file to a different encoding than is in the mysql config file, don't
you risk
On 5/29/07, David Smith [EMAIL PROTECTED] wrote:
My exprience shows that it may be necessarily to specify encoding for
mysql in dburi.
The reason is that mysql server may be configured with default encoding
that doesn't match the database you're connecting to. E.g. if you open
mysql
The first thing is to see what MySQL thinks its server and client
character sets are:
$ paster shell development.ini
import pylons.database
engine = pylons.database.create_engine()
engine.execute(SHOW VARIABLES).fetchall()
Look for the variables that start with character_set_ and
collation_.
Hi Mike,
Thank you for all the details. I've seen the merits of the arguments and I
guess the conclusion is these points:
1) The MySQL specific option of use_unicode is not needed anymore. The MySQL
specific charset option also is deprecated.
2) The SQLAlchemy convert_unicode option is
On 5/11/07, andyprog [EMAIL PROTECTED] wrote:
Hi all,
(I'm using Pylons for the first time, so pls bear with me...)
I'm setting up a Pylons app with Mako + SQLAlchemy + MySQL + UTF-8
support
-- but I've had trouble finding one place with clear instructions on
how to do this,
so I've
Thank you for your answers, Max and BJPirt.
I'm going to set things up and I'll let you know how it went.
Andy P
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
pylons-discuss group.
To post to this group, send
11 matches
Mail list logo
