Question: We all have our favourite database. If you look objectively at your chosen database, what drawbacks does it have and what could be improved?

The rules:

* One reply per drawback with;
* a short description of the limitation, followed by;
* a more detailed description, an explanation of how it could be done better or an example of another technology that does not have the same limitation.
* Do not diss any database that you haven't used extensively. It is easy to take potshots at other technologies but we want to learn form your experience, not your prejudice.

Answer: 
**Database** Oracle

**Problem** Temp table definitions are not private

**Description** Many databases (eg Postgres and Sybase) allow you to create temp tables on the fly, insert into them, add indexes if you want, then query from them. Oracle has temp tables, but the temp table definitions exist in a global name space. Therefore the temp table has to be created by a DBA, you need to synchronize between the table definition they used and your code, and if two pieces of code want similar (but not identical) table definitions, they need to use different names. These differences make temp tables far less convenient for developers.

Yes, I understand the benefits for the query optimizer of having global definitions. However for me the lack of convenience makes Oracle's temp tables virtually useless for me, while I use them very intensively in Postgres.
**Database** Postgres

**Defect** No analytic queries

**Description**

Analytic queries, introduced by Oracle, are part of the SQL 2003 standard. Unfortunately Postgres hasn't implemented them yet.