in reply to Twin interfaces, and one and a half databases to a project

The Man has cooked up a poor design. It breaks normalization of the database, creating synchronization problems and providing a definite security problem to replace a speculative one.

The solution is dependent on the RDBMS, but starts with providing several levels of privilege in db access to correspond to the cgi groups.

If you can't talk him out of his notion, you may be able to devise an implementation in terms of slave db's mirroring a master copy.

After Compline,
Zaxo

  • Comment on Re: Twin interfaces, and one and a half databases to a project

Replies are listed 'Best First'.
Re: Re: Twin interfaces, and one and a half databases to a project
by vladb (Vicar) on Aug 15, 2002 at 18:40 UTC
    But setting up slave db to mirror a master copy may not work either. I figure that the Man wants only portions of the master being replicated. Further, data boundaries are determined by user priviledges. That is, he doesn't simply want to copy table C and leave tables A and B on the main server. It seems like they want to copy portions of various tables.

    But you are right, this is a dangerous path. My best bet would be to definitely create multiple database groups and tablespaces (for Oracle) or separate databases (for MySQL). Have certain cgi scripts run as user Z who's only allowed to access database X. Appears pretty secure to me! :).

    Well, the contractor could always ditch the project and search for greener (sane) pastures ;-)

    _____________________ 
    # Under Construction

    [download]
[reply]
[d/l]

In Section Meditations