Given that I've never even heard of CUBRID before your post... no,
there aren't any plans.
More broadly, there aren't really any plans to add extra database
backends to Django's core itself.
Instead, we're encouraging a community of database backends to flourish.
Our built-in set of SQLite, MySQL, Postgres and Oracle gives us
coverage of the most widely used open source databases, and one major
commercial database. This enables us to claim, from a marketing
position, that we are a cross-database solution.
Then, there are external backends available for DB2, Sybase
SQLAnywhere, MSSQL, Firebird, and others. These projects exist
entirely outside Django's source tree, and they have their own release
cycles, maintainers, and so on.
If CUBRID is something that you think is important, then I encourage
you to write a database backend to support it. If CUBRID provides a
Python DB-API compliant interface, and contains a well-featured SQL
implementation, it should be fairly easy to write such a backend.
However, if it turns out that CUBRID has some eccentricity that
requires a modification to the Django database backend API, make a
proposal and we'll consider it.
Yours,
Russ Magee %-)
There are no plans I know of, and I for one have never heard of it until
now. That suggests it doesn't have a huge amount of market share, and
not enough to warrant a backend included in core as yet.
Luke
--
"I have had a perfectly lovely evening. However, this wasn't it."
(Groucho Marx)
Luke Plant || http://lukeplant.me.uk/