in performance or integration (like foreign keys).
>
> in brief, postgres tries to be standards compliant - so if you are
> worried about standards ...
Note that with MySQL does try too..
--
Geert Vanderkelen
http://some-abstract-type.com
--~--~-~--~~~-
)
For Django however, it shouldn't matter what you choose.
Cheers,
Geert
--
Geert Vanderkelen
http://some-abstract-type.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post t
get_template('app1/index.html')
It should work fine:
- Non name clash
- And you can customize
--
Geert Vanderkelen
http://some-abstract-type.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django us
ne: a Django cheat sheet:
>
> <http://www.mercurytide.com/whitepapers/django-cheat-sheet/>
Awesome! Thanks for sharing this!
If only I had that this morning while on the train! :)
Cheers!
Geert
--
Geert Vanderkelen
http://some-abstract-type.com
--~--~-~--~~--
yourself a new hoster or upgrade to at least
MySQL 4.0.. The Django backend might not work forever with old
MySQL versions like 3.23..
Cheers,
Geert
--
Geert Vanderkelen
http://some-abstract-type.com
--~--~-~--~~~---~--~~
You received this message because you
nteresting :)
We have it here on our website:
http://www.mysql.com/products/database/maxdb/
There are some modules for interacting with MaxDB, so maybe one can make
a Django Backend? I can't dig into that but I forwared this post!
Geert
--
Geert Vanderkelen
Unicode (utf8)
Did you forget to do
mysql> SET NAMES 'UTF8";
when selecting in your client?
Cheers,
Geert
--
Geert Vanderkelen
http://some-abstract-type.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
et me know. Patch looks good to
me, will put more time in when I get back next week.
Cheers,
Geert
--
Geert Vanderkelen
http://some-abstract-type.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django
columns with a
specific character sets, then following place in the manual is
important:
http://dev.mysql.com/doc/refman/5.0/en/charset-connection.html
Cheers,
Geert
--
Geert Vanderkelen
http://some-abstract-type.com
--~--~-~--~~~---~--~~
You received
h 4.1, you should use 4.1. This is because
things like PHP et al. are linked against 4.1 libmysqlclient.
Hope this helps,
Geert
--
Geert Vanderkelen
http://some-abstract-type.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed
acter buffer, not
> array.array
>
> It seems mysqldb's problem
Can you say what tables you change and how? What ALTER TABLE did you
use? Maybe I can check it out.
Geert
--
Geert Vanderkelen
http://some-abstract-type.com
--~--~-~--~~~---~--~~
You received
probably upgraded MySQLdb over an
older version. You need to remove set.py from the MySQLdb 1.2.1 installation.
I reported it here:
http://sourceforge.net/tracker/index.php?func=detail=1445105_id=22307=374932
Hope this works.
Cheers,
Geert
--
Geert V
ome replication going and daily backups in place. Never trust your or
others hardware..
Cheers,
Geert
--
Geert Vanderkelen
http://some-abstract-type.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django use
maller and
faster!). If you need high availability of your data, you can go MySQL
Cluster. Need a data to /dev/null, use the blackhole engine! ;)
Anyway, whatever you choose, choose the one you are most comfortable with!
Cheers,
Geert
--
Geert Vanderkelen, Support Engineer
MySQL GmbH, Germany,
James Bennett wrote:
> On 6/28/06, Geert Vanderkelen <[EMAIL PROTECTED]> wrote:
>> I'm also not sure how you going to use the full text
>> searching unless there is a patch now too..
>
> For just querying against the DB, having fulltext indexes set up
> should
full text
searching unless there is a patch now too..
Cheers,
Geert
--
Geert Vanderkelen, Support Engineer, MySQL AB
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to t
ere or so..
MyISAM -> none transactional
InnoDB and NDBCluster (and BDB) -> transactional
Using InnoDB you can do transaction, using MyISAM not.
Cheers,
Geert
--
Geert Vanderkelen, Support Engineer
MySQL GmbH, Germany, www.mysql.com
--~--~-~--~~~---~--~~
You
eck last few comments :)
Looks only affecting Windows for now.
Cheers,
Geert
--
Geert Vanderkelen
http://www.some-abstract-type-shit.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django user
YSQL is rejecting ?
Could be.
- Exact MySQL version?
- which encodings are you using?
- SHOW CREATE TABLE yourtablename\G
- What is default charset on server? SHOW GLOBAL VARIABLES LIKE 'char%';
--
Geert Vanderkelen
http://www.some-abstract-type-shit.com
--~--~-~--~~~--
e'll end up with WEIRD errors that only
> occur with migrated databases...*grin*
Thanks for pointing that out! They were changed to VARCHAR(100) and just
fixed it in the wiki.
I'll do a DDL diff tomorrow and eventually add more stuff.
Cheers,
Geert
--
Geert Vanderkelen
http://www.so
ree to pitch in!
I just fixed the renaming of the columns for MySQL in the wiki:
ALTER TABLE django_content_type CHANGE package app_label VARCHAR(20) NOT
NULL, CHANGE python_module_name module VARCHAR(50) NOT NULL;
(Note: both operation are in the same statement.)
Cheers,
Geert
--
Geert Vand
which has was recently
being 'upgraded' to use more MySQL 5.0 stuff.
Cheers,
Geert
--
Geert Vanderkelen
http://www.some-abstract-type-shit.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users"
are not alternatives since the ALTER TABLE .. RENAME is for tables
only :)
You got my vote in correcting these two lines there, but need to make
sure it's going for the other DBMSes too..
-Geert
--
Geert Vanderkelen
http://www.some-abstract-type-shit.com
--~--~-~--~~--
idea: dump data using
mysqldump of MySQL 5.0, and reimport is best.
Going first 4.1 might be better, and check all ChangeLogs in the
manual.. might be important for your stuff!
Cheers,
Geert
--
Geert Vanderkelen
http://www.some-abstrac
The GLOBAL keyword is important, as it will default to SESSION, and of
course that stays zero as you have another session in the MySQL client.
Hope this helps!
Cheers,
Geert
--
Geert Vanderkelen
http://www.some-abstract-type-shit.com
--~--~-~--~~~---~--~~
t this, I guess others can comment..
Hope this helps!
Cheers,
Geert
--
Geert Vanderkelen
http://www.some-abstract-type-shit.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To pos
91 this is done in django/core/db/backends/mysql.py.
You will need change it there right now, or introduce
DATABASE_ENCODING in your settings.py and use that..
Hope this helps.
Regards,
Geert
--
Geert Vanderkelen
http://Kemuri.Org
--~--~-~--~~~---~--~~
You
27 matches
Mail list logo