oracle

Hello Enterprise group! I have extensive experience with enterprise systems like JD Edwards, Oracle, and SAP, in manufacturing and now I'm a Drupal developer. I would like to start a discussion about Drupal's ability to replace these proprietary systems. I suffered many years dealing with these systems and would love to see Drupal put the RIP label on their strangle hold on industry. I'm especially interested in:
1) What does Oracle/SAP/etc do that Drupal can't do?
2) What parts of Oracle/SAP/etc can be replaced by D7? D8?
3) Are you using Drupal in your enterprise now? If so, how?

Hi all,
i'am one of the guys who is triyng to build an oracle driver for drupal.... (http://drupal.org/project/oracle)
I actually wrote 2 drivers: 1 for the 6.x and 1 for the 7.x. Both based on PDO_OCI, and both working pretty
well with the core, (i'am still working on the 7.x SimpleTest test cases but 90% is ok).

I started using the 6.x driver in production on February (when it was on sourceforge.net as drupaloracle).

A couple of days a go, one of my company web developers, told me:

"Hey.. we should use this X module.... It is cool!"

Abstract

Drupal 6.0 is revamped with Schema API, so what's next for Drupal 7.x? PDO for sure! With this powerful data-access abstraction layer, workload will much reduced for DB abstraction layer designers and developers, and finally benefit our contribute developers and end users.

By the way, together with the decision of Drupal 7.x + PDO, there is also some voice about moving PostgreSQL (and so other potential databases support, e.g. Oracle, DB2, MSSQL, etc) support away from core, but contribute; on the other hand, add official SQLite support into Drupal core, together with MySQL.

Is this really a good idea? Or even if it is possible? As an existing Drupal + PostgreSQL users, what will this affect your daily work? As a potential customer of Drupal + Oracle/DB2/MSSQL/etc, is this a good new for you, or just an evil? I would like to provide some brief idea for you within this article.

After over 1.5 years of development (since 29/11, 2005), plus number of developers contribution, and help of Drupal 6.x schema API, a new Oracle driver for Drupal 6.x is now ready for testing.

The latest version of Oracle driver overcome a lot of Oracle-specific limitation, and able to work well as like as existing Drupal database driver, e.g. MySQL and PgSQL.

Ok, i'll be the one to call the pink elephant in the room.....stored procedures do exisit. There I said it. :). With MySQL 5 starting to support them, Postgres has had them, and the push latley to start using a wider array and more robust DB's (oracle, mssql, DB2), it is time I think to start thinking about a database abstraction layer to handel stored procedures. I'm thinking perhaps something like this:

/**
* @param $proc_name Name of the stored proc.
* @param $args Argements to send to the proc indexed by the variables name. e.g. array('name' => 'Jim Smith');

So I have 2 Oracle installations running great on 4.7.3, and 4.7.4.

So I thought 5.0 would be easy to tackle....totally wrong.

I was on the phone with Oracle late tonight. I'll try and keep this rant short. But, the reason that Oracle will work with 4.7 and not 5.0 is that in 4.7, you have to run your SQL statements manually, and in 5.0 Drupal does this for you. This is a really nice feature. However, that's where the problem comes in:

Currently, the Oracle implementation use sequences and triggers to simulator auto_increment and serial fields. The problem is that you can not create a trigger from PHP, you much run a trigger DDL from Oracle's SQL+ (or if you have Java). For some reason, it's a bug in the oci8 module.

I have started some "step-by-step" handbooks on running drupal on alternative databases (those that are non-standard-drupal).
So far, I have just started Oracle. When I have time, I will try and do the MS SQL one also. I'd love some crituqes on getting this polished off and included in the Drupal.org handbooks.

http://eb3it.com/oracle_handbook

Ok, today I am going to start to consolidate all of these diff. db support tasks into my sandbox for a pre-release and discussion setup. Right now, there are about 5 different, and very good, threads about Oracle and MS-SQL support. However, there is still no central place for everyone to consolidate their code and work on the DB's. This needs to happen so no one goes off and re-invents the wheen. So, today I am going to sift through the threads, integrate as much as the code togather as I can, and commit them to my sandbox.

I personally currently have an Oracle installation and a MS-SQL installation working very well.

Note:I welcome others to join the effort and I will provide some tablespace on an Oracle 10g database server to test and implement an Oracle driver for Drupal upon request

I have begun Oracle Support in full gear. After this, I plan to do the same with MS-SQL. I shall start to release my findings here. I am starting with some code from this ( http://drupal.org/node/39260 ) drupal thread. I'm testing against Oracle 10g.

I have installed Drupal 4.7.3, and I am using the database.oracle.inc, and database.oracle.sql very well. I have full funcitnality thus far.