Wednesday, February 22, 2017

Re: Is this possible with Django, new to this!

Hi,

 

Being modern is hardly ever a good reason to undertake a project and it shows in how you set your requirements.

If however:

  • You have time to spare and want to learn how to create a web application
  • Requirement of the project is that everyone should always have access to the latest information, if they have an internet connection
  • You or your company wants to move away from desktop to internet and have allocated ample resources to transition

then read on.

 

On Wednesday 22 February 2017 01:25:20 ushills wrote:

 

> Can I create a view into a database with approximately 20 fields that

> allows be to drill down into each row and that allows me to view and

> enter transactional information and view an audit path for how each

> row has changed over time.

 

To work with Django, think the other way around. You don't have a database, you have objects (models), with attributes (fields) that happened to be retrieved from and stored in a database. Even though it is possible to work from database to model, this is really to support legacy or 3rd party databases and not the recommended way of doing things.

 

> Essentially, each row will be a component type with various cost

> production criteria, these will be changed over time and in

> combination produce a total cost for the completed product.

 

I'm actually working on that at the moment, using Component, HalfProduct and Product models for the catalog, and Production, Stock and Purchase affecting the costs.

 

> I want users to be able to enter the components, update the cost

> criteria at regular intervals and view the total cost with views into

> each component type to view the audit path of how and who has changed

> the cost criteria.

 

This isn't in my project requirements, so I'm only recording stock mutations. If I had to, I'd switch my custom mutations to one of these audit trail packages.

 

So in conclustion it certainly is possible, but do it for the right reasons :).

--

Melvyn Sopacua

No comments:

Post a Comment