[gnukhata-devel] minits on inventory meeting on 13 August

  • From: Krishnakant <krmane@xxxxxxxxxxxxxxx>
  • To: GNUKhata devel <gnukhata-devel@xxxxxxxxxxxxx>
  • Date: Mon, 15 Aug 2016 09:27:07 +0530

Hello all,

We had a detailed discussion on Inventory module with the team in Pune.

list of attendees:

* Abhijeet Balan,

* Bhavesh,

* Kanchan,

* Prasad,

* Pornima

* Sheetal,

* Vaibhav,

* Krishnakant.


The meeting started with the discussion of unit testing and we decided that the framework will be programmed in tamdum with the current development and with the Inventory module. Kanchan showed keen interest in the unit testing. Pornima will forward the email for testing to the mailing list again, (already done ).

Regarding the inventory we decided to start planning out the database.

The challenge was about dynamic categories with the product table having user defined columns.

This could be achieved in two ways.

Krishnakant suggested that we either create dynamic tables by the name of that category and put the spects in those individual tables.

Then create dynamic relations with the stock table having actual stock details.

Or we could have a single table with productcode, specification and category_code field.

the specification field will be of type json.

This might be an advantage even for searching.

The entire team will look at jsob datatype more closely and study how keys are searched and how the value is fetched.


How the category table will be created was also discussed.

The table will have a category_code, category_name and subcategoryof fields.

Should we have a list of fields available in the product table in the category table table to give a hint of what we have?

We concluded the meeting by deciding to make trial models and then decide on the best possible one.

Pornima will be coordinating from Pune.

Prasad and Bhavesh had started to think on the GUI part and will be expected to take up the challenge of the same during the inventory module as wel.

Happy hacking.

Krishnakant.

Most team was in favour of the latter and is under consideration.



Other related posts: