[sesha] Stock ID

[Nik Chanda]

Hi Jan--

We are currently working to extend the functionality of sesha back 
toward an asset management application, so we have added a couple 
linking tables using the stock_id.  The stock_id in our data model is 
never used other than an internal primary or foreign key, so we agree 
that this should be hid from the user.

I think though that the intent was to allow the user to determine a 
different stocking schema than an auto-incremented integer.  In that 
case, maybe there should be a SKU number or equivalent added to the data 
model that replaces the "Stock ID" search functionality.

Nik


Jan Schneider wrote:

>Hi,
>
>is anybody using the stock id differently than an incrementing counter? 
>It can only take an integer at the moment, so you can use any internal 
>numbers, it is the primary key of the inventory table, so you shoot in 
>your feet if you enter a wrong value, but you still have to provide it 
>manually every time.
>
>I would like to hide the id completely and use it only internally, any 
>objections?
>
>Jan.
>
>  
>