Hello,

We are a small startup producing organic food. I want to use Tryton in a
for inventory management and later for accounting.

In food and especially organic food it is essential to exactly track all
the lots.

In the stock.moves table is all the information needed, but i need a way
to display the history of a specific lot in the sense of what lots were
used to produce it and what lots were used to produce them and so on
until the shipment the ingredients came with.

So it is going to be a big tree, that is not possible to know before.
After quite a lot of reading, i see three possibilities to approach the
problem:

1. owerwriting table_querry() in a new ModelSQL:

i could join several tables to have all relevant information in one
model, but i have to filter the records in steps and in each step
finding the parents of the curent lot, and only then i can start finding
the grandparents. I don't know how to filter the table with in such a
way, witch is (i think so) not possible with a Domain or a where-clause.

2.overwriting read() in a new ModelStorag:

i was reading about this possibility in the mailing-list
(https://www.mail-archive.com/[email protected]/msg06049.html).
This way I can build the list of records as i need it. But read() gets
ids as an argument, and i don't know were the ids come from. And before
the read() is called and the tree is build, it is impossible to know how
many records will be there.

Is it possible to use the read() method anyway ignoring ids?

3. using  babi or hebi

 could perhaps solve my problem. But these are quite complex modules
with little documentation, so it would be nice to get a hit from
insiders whether it is worth diving into (and witch of them) to get a
solution.

This is what i found so far, but perhaps there other possibilities i
don't know of?

Regards and Thanks for your help,

Ulrich


-- 
You received this message because you are subscribed to the Google Groups 
"tryton" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tryton/f26d3699-a91e-9c6d-2f74-67af5b65cd17%40gmx.de.

Reply via email to