Tag Info

New answers tagged

0

As datagod points there's a legality component towards the practice of storing sensitive information such as a passport number. Where I live an active enforce of UK law Data protection act is the standard practice. But in other places like Chile is totally legal to store passport number which is the same as the ID (RUN), some websites even offer the ...


5

As stated in comments, I agree with @Erik and you should normalize the structure of your database defining a specific table to store Order data and another table to store Address related information. The resources previously used to illustrate the approaches suggested here were scattered in different external links, so I have integrated them into a single ...


4

This answer was compiled from comments to the question. One solution would be to use a FK to the address table in the order table. That will let you see the addresses that were used for the order, and decouples the address from the User's current address. In order to make this work you would have to insert a new address and link that new address to the ...


0

At 250/hour, all possible techniques are plenty fast. Anyway, I will throw my 2 cents in... Multi-row INSERT of 100 rows will run 10 times as fast as 100 individual INSERTs. Multi-row INSERT may lead to gaps in AUTO_INCREMENTs. In general, the command will preallocate all the ids it might need, then 'burn' the ones id did not use. (REPLACE them all dups ...



Top 50 recent answers are included