Movable Type & Oracle - Can They Work Together?
April 28, 2004 2:55 PM   Subscribe

How easy is it to get Movable Type to work with Oracle? I would like to use this at work but it wouldn't be acceptable with a MySQL or Berkeley DB. How difficult would it be? Should I just wait and hope that it's supported with Movable Type version 3?
posted by adoran2 to Computers & Internet (4 answers total)
 
The requirements page says they use perl, which I assume means they use DBI.(interesting how hard it is to type a . instead of a ; after use DBI). There's a DBD for oracle, so it shouldn't be that much work.

On the other hand, why would you want to? For the kind of stuff Movable Type does Oracle just isn't necessary, and I doubt it'll be faster either. If it's because you already have oracle installed and you don't want to install MySQL or your webhost won't let you, just use Berkeley DB.

The right tool for the right job. Or, considering it's movable type, at least The right tool for the wrong job.

*ducks fast and runs*
posted by fvw at 3:28 PM on April 28, 2004


Best answer: We have a number of installs of people who are using the DBD for Oracle with MT 2.x (and it should work similarly with MT3) even though, as pointed out, it's largely overkill. Typically, the rationale is that they're paying for the database, so they want to get as much use out of it as possible, and I can't really argue against that.

Feel free to email me at anil at sixapart dot com if you need any specific advice on this.
posted by anildash at 4:28 PM on April 28, 2004


Shouldn't be a matter of simply redeclaring a line somewhere that gives a data source string?
posted by namespan at 4:51 PM on April 28, 2004


Provided they don't use any database-specific features or behaviours, yes. (which, generally, means "no". But seeing as they also accept berkeley DB, there's a chance it really is yes)
posted by fvw at 8:16 PM on April 28, 2004


« Older SQL Injection Security Issues   |   TV tuning and reception Newer »
This thread is closed to new comments.