Re: Django for in-house data

You haven't said what DB product you are connecting to.

However, why don't you use a tool that is designed to allow end users as
well as syrems folk to interact with data - check out Pentaho - BI and
DI applications and dashboards, reports etc. There is an open source
version. You can implement security, if required.

Letting end users directly access the DB is quite wrong, especially if
the DB is complex. In the latter case, many of the reports created will
be wrong, and decisions will be made on misleading data.

Robin St.Clair


On 09/12/2013 09:01, Lachlan Musicman wrote:
> On 9 December 2013 19:17, Mike Dewhirst <miked@dewhirst.com.au> wrote:
>> On 9/12/2013 8:14am, Lachlan Musicman wrote:
>>> To be fair, I think the best measure is the technical literacy of your
>>> users. The Admin interface is powerful, but they could also
>>> accidentally screw everything up.
>>
>> Your point about technical literacy bears thinking about. Wouldn't you say
>> all users can screw things up whether they are technically literate or not?
> Of course - I've even done it myself. But some users are more likely
> to than others. More importantly, they are usually less able to
> articulate exactly what it was they did to enact the data loss.
>
>
>
> Cheers
> L.
>
>
>

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/BLU0-SMTP4620FB3B74146705DC9690AE2D30%40phx.gbl.
For more options, visit https://groups.google.com/groups/opt_out.