On 24.09.2012 09:13, Randall wrote:
Hello Trac Developers,
I am involved in planning out getting Trac to work on a NonStop server.
We are working on the preliminaries (porting a good version of Python
and database support in there). I was wondering if there are any gotchas
that I need to watch out for in trying to port to a new database engine?
The native SQL is SQL/MX, which is fast and large, ANSI 2003 compatible,
full transactional support with statement isolation.
Are there some resources I can look at for the database?
The overview page for the IDatabaseConnector extension point [1] links
to some discussions about creating backends for other database engines.
Besides the Oracle and MS SQL tickets, there's also [2] which summarises
the problems the Oracle_cx backend ran into:
* Lack of Autoincrement type
* CLOB columns in Indexes not supported
* CLOB can't be in PK's and length of PK is limited
* Different syntax of parametrized SQL
* Lack of LIMIT/OFFSET keywords in queries
* Oracle keywords as Table/Column names
* Parameter size limitation
Another idea might be to browse MySQL backend tickets. [3]
--
Peter
[1]
http://trac.edgewall.org/wiki/TracDev/PluginDevelopment/ExtensionPoints/trac.db.api.IDatabaseConnector#AdditionalInformationandReferences
[2] http://trac-hacks.org/ticket/5487
[3]
http://trac.edgewall.org/query?keywords=~mysql&status=!closed&or&keywords=~mysql&resolution=fixed&group=status
--
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/trac-dev?hl=en.
