Tag Info

New answers tagged

1

You should store any value using its ISO measure unit. Calculations and conversions should be done at the client side. Don't expect any performance gain over client side conversion when using computed columns. As far as passing in data in any measure unit, I advise against that design: make the client pass in the data in the ISO measure unit and do any ...


0

Colin 't Hart is correct. Do not mix data in your table names. Instead, create a Carrier table consisting of an identifier and the name of the carrier. TABLE "Carrier" ID | Carrier 22 | Carrier1 31 | Carrier2 Reference the carrier in the weight price and shipping departure tables via the identifier as a FK. So in the case of the weight price table ...


0

"Compressed MyISAM" -- what is that? Maybe "Archive"? Compression is not needed; the tables are too small, and will quickly be fully cached. FOREIGN KEYS -- Why? You have debugged you code, haven't you? There will be no dangling things to check. MEMORY is not unreasonable, if you write 'reload' code that executes whenever you bring up the server, and any ...



Top 50 recent answers are included