On 08-Aug-07, at 10:13 PM, James Bennett wrote:
>> constructing the SQL. With Django, it is building the SQL for me.
>
> Your best bet is to thoroughly read the documentation on the ORM; once
> your tables are created (it can create them for you, but you don't
> have to let it do that -- instea
On Aug 8, 9:49 am, Stephen Bunn <[EMAIL PROTECTED]> wrote:
> I know it obviously needs to be able to execute SELECT, UPDATE, and
> INSERT statements, but what about ALTER? SHOW? does it need to create
> views? create indexes? what about locking tables and creating temporary
> tables?
The true min
On 8/8/07, Stephen Bunn <[EMAIL PROTECTED]> wrote:
> Understandable. But for somebody new to an ORM type model (like me)
> things might not be so clear. If I am writing a PHP or Perl
> application, I know exactly what permission it needs because I am
> constructing the SQL. With Django, it is b
Steve,
SB> Perhaps I am wrong, or just going about this the wrong way, but I have
SB> been looking the Django documentation and asking around in #django and
SB> nobody can (or do not want to) give me a straight answer and the minimum
SB> database permissions Django needs to operate. So I am
Kenneth Gonsalves wrote:
>
>
> you have to divide the tasks into those that you want to do through
> django and those that you want to do outside django - django needs
> permissions to do the first set. I dont think one can be clearer than
> that.
>
Understandable. But for somebody new
You need certain permissions to setup the superuser account, although I
don't know which, only Select,Update and Insert are not enough for setup the
superuser account.
On 8/8/07, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
>
>
>
> On 08-Aug-07, at 7:19 PM, Stephen Bunn wrote:
>
> > therein lies t
On 08-Aug-07, at 7:19 PM, Stephen Bunn wrote:
> therein lies the problem. What is 'everything' that Django
> requires to
> be done?
>
> I know it obviously needs to be able to execute SELECT, UPDATE, and
> INSERT statements, but what about ALTER? SHOW? does it need to create
> views? create i
Kenneth Gonsalves wrote:
>
> On 08-Aug-07, at 6:51 PM, Stephen Bunn wrote:
>
> use whatever permissions you are happy with. As long as the user
> under which django accesses the database, can do everything django
> requires to be done, it's fine. I dont think this is any different
> from a
On 08-Aug-07, at 6:51 PM, Stephen Bunn wrote:
> Is there any documentation anywhere that describes setting up correct
> database permissions for use with Django.
use whatever permissions you are happy with. As long as the user
under which django accesses the database, can do everything django
9 matches
Mail list logo
