One Schema Definition for Multiple DB Engines!

[figment]

I am looking for a way to define a Database Schema once.
And then have an automated database setup script read that definition and appropriatly create DB tables in whatever PEAR DB the user has selected.

The reason I ask, is because I cant just create a table in MySql with PHPmyAdmin, and export the schema and then expect that to work in say.. Postgresql, or oracle...

Can I?
Hod do i solve this problem?

[mattr]

Well, you could store the schema in a vendor-neutral format...

Like create an application which allows you to specify the schema in a generic format -- e.g.:

table name
column1, datatype{ integer, string }, length
column2, ...

Then you have the application generate SQL based upon which DBMS you are using -- you can map integer -> number in Oracle, integer -> int in MySQL, etc.

[dopp]

check in the PHP documentation about the database abstraction layer. I think this is what you are trying to talk about. =)

[figment]

I am already using database abstraction.

Here is my situation.
I am writting a web application that will create tables with a static schema to store information the application generates (its a web blog app).

My issue is the initial setup, the admin user wil typ the names for the tables, orleave the default (i blieve in options), and then press a 'Create Table' button.

My issue is not the database abstraction itself, I have so far succesfully integrated PEAR's DB into the application, to the point where im doing an fopen() on the driver directoy, so that no matter where its installed, it has sutomatic support for whatever DBdrivers are installed.

The issue is that my experience is ONLY with MySql, and i guess my real question was hit upon by mattr:

Originally posted by mattr
Well, you could store the schema in a vendor-neutral format...

Like create an application which allows you to specify the schema in a generic format -- e.g.:

table name
column1, datatype{ integer, string }, length
column2, ...

Then you have the application generate SQL based upon which DBMS you are using -- you can map integer -> number in Oracle, integer -> int in MySQL, etc.

is there a reference i can use to make a create table statement vendor neutral?

or an app out there already written?
id rather not write this myself as its out of scope of my interest, and the project itself, btu i will if i have to.

I guess the main idea is compatability with the PEAR DB no matter what upgrades, or changes to the instaled system are made.