RE: [PHP] Database Administration
| From: | Bob McConnell | Date: | Fri, 24 Sep 2010 19:50:41 +0000 |
| Subject: | RE: [PHP] Database Administration | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-308301@lists.php.net to get a copy of this message | ||
From: tedd
>At 2:36 PM -0400 9/24/10, Bastien Koert wrote:
>>On Fri, Sep 24, 2010 at 2:26 PM, tedd <tedd.sperling@gmail.com> wrote:
>>> At 2:09 PM -0400 9/24/10, Bastien Koert wrote:
>>>>
>>>> @tedd,
>>>>
>>>> He wants not techie users to create new systems for their clients
when
>>>> they sign up. It involves creating a DB and he's wondering about
>>>> security for that. The main part of the app needs the least priv's
to
>>>> run (select, update, insert [,delete]) while the creating the DB
>>>> obviously takes more. The OP was asking how to best handle that
since
>>>> the he didn't want to give the main app DB user account more privs
>>>> than needed.
>>>
>>> Okay, what does creating "new systems for their clients" mean?
>>>
>>> What I want to know is specifically what these non-techie users
intend to
>>> do?
>>>
>>> Please don't answer that they want to set up accounts for their
clients
>>> because that is meaningless to me. That could mean anything.
>>>
>> > So, what specifically are these non-techie users going to do?
>>
>>Create a DB schema, create and populate tables.
>
> Creating a DB schema is not for non-techies -- you really need to
> know what you are doing to do this.
>
> But we all live with what we create.
I suspect he actually means create a new table using a predefined
schema. But unfortunately, he doesn't appear to know enough about the
problem to be able to explain it. He is either in way over his depth, or
hasn't done a very good job of defining his requirements.
Bob McConnell