Thank you for kind response.
> flexible enough to handle any database-specific configuration. Would
> you be willing to code up a patch?
Yes, of course! Even I have already posted the one:
http://code.djangoproject.com/attachment/ticket/2866/ticket2866.diff .
# In the diff, I did not tested modi
On 11/1/06, Yasushi Masuda <[EMAIL PROTECTED]> wrote:
> DATABASE_ENGINE = 'sqlite'
> DATABASE_NAME = 'mydb'
> DATABASE_OPTIONS = {'charset': 'utf8'}
> ...
>
> I think this allows user-level flexibility in DB configuration, rather
> than beating out the ultimate universal default configurat
On 11/1/06, Yasushi Masuda <[EMAIL PROTECTED]> wrote:
>
> As in the ticket #2866, I think it would be nice if DatabaseWrapper has
> extra keyword options, which are passed to individual DB-API connection
> object constructor.
+1
I had been thinking about putting a patch together for the MySQL
ba
As in the ticket #2866, I think it would be nice if DatabaseWrapper has
extra keyword options, which are passed to individual DB-API connection
object constructor.
For example, MySQLdb allows "charset" option that can be used to
determine default_character_set of a connection. Pysqlite has
are ti
As in the ticket #2866, I think it would be nice if DatabaseWrapper has
extra keyword options, which are passed to individual DB-API connection
object constructor.
For example, MySQLdb allows "charset" option that can be used to
determine default_character_set of a connection. Pysqlite has
are ti
