Re: Django for in-house data

2013-12-09 Thread Lachlan Musicman
On 10 December 2013 00:23, wrote: > What I'm trying to understand now is it's possible with little effort to > build views which mostly behave as the admin interface would, doing some > customization on specific points where needed. > > For example, the paged views offered by the admin interface

Re: Django for in-house data

2013-12-09 Thread Mike Dewhirst
On 10/12/2013 12:23am, giuliano.bertole...@gmail.com wrote: the database is built from scratch, so I can use whatever I wish. Currently I'm performing some tests with SQLite, but plan to migrate to MySQL for production. The project is building a basic CRM with a few tweaks for managing specific b

Re: Django for in-house data

2013-12-09 Thread giuliano . bertoletti
the database is built from scratch, so I can use whatever I wish. Currently I'm performing some tests with SQLite, but plan to migrate to MySQL for production. The project is building a basic CRM with a few tweaks for managing specific business types. I'm new to Django and Web frameworks i

Re: Django for in-house data

2013-12-09 Thread Robin
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 implemen

Re: Django for in-house data

2013-12-09 Thread Lachlan Musicman
On 9 December 2013 19:17, Mike Dewhirst 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 tech

Re: Django for in-house data

2013-12-09 Thread Mike Dewhirst
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. I agree that the Admin is not for general use. What I was thinking about was the spe

Re: Django for in-house data

2013-12-08 Thread llanitedave
It wasn't in Django, but I previously developed a very large and complex database and gave administrative access to just a few too many people. They had the best of intentions -- no sabotage involved, but they still managed to screw up the records royally. Lesson learned -- NEVER give blanket

Re: Django for in-house data

2013-12-08 Thread Lachlan Musicman
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. Views (can) remove that opportunity L. On 9 December 2013 08:06, Mike Dewhirst wrote: > On 8/12/2013 9:15pm, giuliano.bertole...@g

Re: Django for in-house data

2013-12-08 Thread Mike Dewhirst
On 8/12/2013 9:15pm, giuliano.bertole...@gmail.com wrote: Hello, I'm using Django to have people in my company access our database. Since the application is not meant for public use, I was wondering how to best struture it. The admin framework seems to be well suited for manipulating tables via w

Django for in-house data

2013-12-08 Thread giuliano . bertoletti
Hello, I'm using Django to have people in my company access our database. Since the application is not meant for public use, I was wondering how to best struture it. The admin framework seems to be well suited for manipulating tables via web, while views (in my understanding) seem better for