On 10/26/05, Dave Thacker <dthacker@omnicorporate.com> wrote:
>
> IDS 9.4FC6 on AIX 5.3. ISQL 7.32FC2
>
> [...]
>
> Schemas:
> create table "informix".bar
> (
> [...]
> );
>
> create table "informix".foo
> (
> [...]
> );
>


It's probably unfair to pick on Dave, but he's (unwittingly) offered me the
opportunity to make the comment:

As a general rule, user informix should neither own 'operational' databases
nor any user tables (as distinct from the system catalog tables) in the
database. It makes it impossible to separate the multitude of roles that
user informix already has (DBSA, DBSSO, AAO - and this adds the DBA role).
You should create a separate user ID to own and administer the database.

There are going to be times when this is impossible - and Dave may be in
such a bind. For example, the company may baulk at creating any new user ID
- and were probably unhappy when user informix was added. However, even
then, you might have to create the database as informix (though why not as
yourself), but all the tables could be owned by a non-existent user ID.

--
Jonathan Leffler #include <disclaimer.h>
Email: jleffler@earthlink.net, jleffler@us.ibm.com
Guardian of DBD::Informix v2005.02 -- http://dbi.perl.org/
sending to informix-list