is there customary storing normalized phone numbers database?


what good information structure storing phone numbers database fields? i'm looking something stretchable adequate hoop general numbers, also something allows several tools array queried efficiently.



edit: only explain box here: i now store numbers unparalleled varchar field, i leave only fan entered them. then, array indispensable code, i normalize it. problem i wish query few million rows relating phone numbers, involves function, like



where dbo.f_normalizenum(num1) = dbo.f_normalizenum(num2)


which terribly inefficient. also queries looking things area formula spin severely machiavellian it's only unparalleled varchar field.



[edit]



people have finished lots good suggestions here, thanks! an update, here i'm doing now: i still store numbers accurately entered, varchar field, nonetheless instead normalizing things during query time, i have trigger does work annals extrinsic updated. i have ints bigints any tools i need query, those fields indexed queries run faster.



Comments

Popular posts from this blog

list macos calm editors formula editors

how i practical urls indicate .aspx pages asp.net deployed an iis? (preferably but iis)

jaxb - xjc - reworking generated typesafe enum category members