Re: [Web-erp-developers] Re: Level Description

[Phil D. <ph...@du...>]

> But I see this as a workaround and when things get complicated with lots
of taxathaurisations with lots of artificial created level to get the stuff
done  then are the web-erp users stuck in a very big confusing
administration.
> A structural stable solution is to keep a separate table (looks like your
other suggestion) with two columns:
> stockid
> taxauthlevelid

Think of the additional input required too....

>
> For this solution you should understand that in this case you have a very
storage saving technical primary key taxauthlevelid column compared to the
two columns primary key
> taxauthorizationid + level in the taxauthlevel table.
>
> Concerning your search for the two columns primary key, I do not
understand where you find which taxauthority is applicable for the level
registrated at the stockmaster for a specific stockid. Do I miss something?
>

we will only be ever inquiring on this table to get the applicable rate of
VAT/GST or whatever we call it. For this we will need the TaxAuthority and
the TaxLevel, it matters not that TaxLevel is in one table and TaxAuthority
is in another - the index on both fields is actually an advantage for faster
searches in some RDBMS eg SQL Server and Oracle use these indexes. I think
mysql is pretty good with them too.