Does this mean that we cannot at all apply auto increment just on item codes ? Or would it still be possible to create something like transaction references for item code field only, and let sales kit module work as it is ?

I mean instead of inputting the item code manually can't we automate it, how would that conflict with stock id convention.

A complete self join based tree lookup with multiple 'inheritances' would need to be implemented.

So let us keep it simple even if slightly stupid!

As for the auto increment, I will need to implement auto increment number for my project so in the future, maybe I will have some question or suggestion. In my mind now, I will create a table that hold the sequence number for normal item and sales kit. In the normal item form, I will query this table and when the item is inserted, I will increase the number in the database. The only problem is primary key duplication. That way you can define some rule, maybe give some prefix.

If we can replace the primary key id with the stock_id and item_code as a compound primary key in the item_codes table and re-code all the classes and functions to adhere to it, then maybe we can do what you want. It will probably break a few extensions as well!

@joe: good to have.

So what would I need to do for the item codes to get auto populated and have auto increment ?

Is there a little piece of code which I can manipulate without disturbing the whole setup ?

Please let me know.

Thank you,
GJ

The fields stock_id and item_code are both generally VARCHAR(20 except a few of the former are CHAR(20) in all tables they are part of. The varied definition is probably an error or some index justification.

grep stock_id sql/en_US-new.sql

  `item_code` varchar(20) NOT NULL default '',
 `item_code` varchar(20) NOT NULL,
  `item_code` varchar(20) NOT NULL default '',

grep item_code sql/en_US-new.sql

  `stock_id` varchar(20) NOT NULL default '',
  `stock_id` varchar(20) NOT NULL,
  `stock_id` char(20) NOT NULL default '',
  `stock_id` varchar(20) NOT NULL default '',
  `stock_id` char(20) NOT NULL default '',
  `stock_id` varchar(20) NOT NULL default '',
  `stock_id` char(20) NOT NULL DEFAULT '',
  `stock_id` varchar(20) NOT NULL default '',
  `stock_id` varchar(20) NOT NULL default '',
  `stock_id` varchar(40) default NULL,
  `stock_id` char(20) NOT NULL default '',

Though I am not fully at grips with the concept of sales kit and separate item codes within them, I believe if we were to provide a system like that in transaction references where there would be a defined prefix for sales kits and item codes, won't it make them both always unique ? And then even if they were used in combination, they would never conflict I believe.

For example Sales Kit = SK### and Item code = IC###

Even if they were combined ever, they won't conflict.

Now above can only be done if the codes can be both alphanumeric etc.

Hope I am making some sense.

Regards,
GJ

Wonder which field or what logic distinguishes a SalesKit from a normal item......

@joe: this needs investigation.

Just wondering if this has been possible at all ?

I searched wiki but couldn't find anything about auto increment, though when I search in database via php, I can see there is option for auto increment, but if I try to apply it, I get an error.

This would be a helpful tweak if possible at all.

Thank you,
GJ