Thanks for the replies, they have been most enlightening. :)
On Fri, Sep 24, 2010 at 3:50 PM, Bob McConnell wrote:
> From: tedd
>
>>At 2:36 PM -0400 9/24/10, Bastien Koert wrote:
>>>On Fri, Sep 24, 2010 at 2:26 PM, tedd wrote:
At 2:09 PM -0400 9/24/10, Bastien Koert wrote:
>
> �...@tedd,
>
> He wants not techie users to create new sy
From: tedd
>At 2:36 PM -0400 9/24/10, Bastien Koert wrote:
>>On Fri, Sep 24, 2010 at 2:26 PM, tedd 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 creatin
At 2:36 PM -0400 9/24/10, Bastien Koert wrote:
On Fri, Sep 24, 2010 at 2:26 PM, tedd 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
secur
On Fri, Sep 24, 2010 at 2:26 PM, tedd 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
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 [,delet
On Fri, Sep 24, 2010 at 2:05 PM, tedd wrote:
> At 11:19 AM +0100 9/24/10, Tom Barrett wrote:
>>
>> On 22 September 2010 21:40, Bastien Koert wrote:
>>
>>> Not at all. What I would suggest is that you create a separate mysql
>>> user that is used exclusively by the script to do the create stuff.
At 11:19 AM +0100 9/24/10, Tom Barrett wrote:
On 22 September 2010 21:40, Bastien Koert wrote:
Not at all. What I would suggest is that you create a separate mysql
user that is used exclusively by the script to do the create stuff.
The regular application user account should not have those
On Fri, Sep 24, 2010 at 6:19 AM, Tom Barrett wrote:
[snip]
> I'm not actually that familiar with DB admin to that extent. I have either
> app users with lock+crud on specific databases, or root. As a an aside,
> would you know if there is a level of permissions for a user between app and
> root th
On 22 September 2010 21:40, Bastien Koert wrote:
> Not at all. What I would suggest is that you create a separate mysql
> user that is used exclusively by the script to do the create stuff.
> The regular application user account should not have those privileges
> at all.
>
I'm not actually that
At 9:35 PM +0100 9/22/10, Tom Barrett wrote:
Hmm..
I am familiar with PMA. I would for the purpose of this project consider it
too technical for the target user base. The point is to create a GUI layer
that would manage these things.
For example, the 'add client' screen would ask for four thing
On Wed, Sep 22, 2010 at 4:35 PM, Tom Barrett wrote:
> Hmm..
>
> I am familiar with PMA. I would for the purpose of this project consider it
> too technical for the target user base. The point is to create a GUI layer
> that would manage these things.
>
> For example, the 'add client' screen would
Hmm..
I am familiar with PMA. I would for the purpose of this project consider it
too technical for the target user base. The point is to create a GUI layer
that would manage these things.
For example, the 'add client' screen would ask for four things; name,
description, username and password. Th
At 10:48 AM +0100 9/21/10, Tom Barrett wrote:
Hi
I need to build a custom client management app, which will build and manage
a database per client. This means that on top of the usual sql crud, it
needs to be able to create databases, add/edit/delete database users, create
tables.
Is there a wa
[snip]
I need to build a custom client management app, which will build and
manage
a database per client. This means that on top of the usual sql crud, it
needs to be able to create databases, add/edit/delete database users,
create
tables.
Is there a way for me to do this nicely as PHP solution?
Possible. Google phpmyadmin I believe it is completely written in PHP and
does complete database administration (has some weaknesses on stored
procedures though in my view)
Jangita | +254 76 918383 | MSN & Y!: jang...@yahoo.com
Skype: jangita | GTalk: jangita.nyag...@gmail.com
-Original Mes
On 21 September 2010 11:48, Tom Barrett wrote:
> Hi
>
> I need to build a custom client management app, which will build and manage
> a database per client. This means that on top of the usual sql crud, it
> needs to be able to create databases, add/edit/delete database users, create
> tables.
>
>
The DB ist mysql.
No, you didn't understand me clearly.
I need a framework, toolkit, class call it how you want, with wich I develop
an application that administrates the data's in the database. Something like
Smarty but more specific for what I need.
The ideea is the following:
I have 20
uesday, June 26, 2007 3:29 PM
> To: Andy; php-general@lists.php.net
> Subject: Re: [PHP] Database administration framework
>
> > I just need a framework for administrating tables in a
> database. These
> > are simple add/edit/remove operations from tables.
> > Can yo
> Hi,
>
> I just need a framework for administrating tables in a database. These are
> simple add/edit/remove operations from tables.
>
> Can you suggest a framework for this kind of job? Cause there are a lot of
> tables and I hope I can find a nice tool to work with.
>
Look at Qcodo (http://www.
I just need a framework for administrating tables in a database. These are
simple add/edit/remove operations from tables.
Can you suggest a framework for this kind of job? Cause there are a lot of
tables and I hope I can find a nice tool to work with.
What database are you working with? phpMyAd
21 matches
Mail list logo
