How to model an address?

[Gooser]

I've been thinking about addresses, and I'm not sure how I should model it. I've got some ideas, but I'd like to know what others out there are doing. Do you do "address line one" "address line two" "city" "state" "ZIP", or do you further break it down to "house number" "pre-directional" "street name" "street type" "post-directional".

I am very interested in hearing how others have done this.



v/r

Gooser

Why do today
that which may not need to be done tomorrow --me

The Universal Model

 

[mrdenny]

Address1, Address2, City, State and Zip is the usual storage method unless you have a real need to break it down further.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[r937]

breaking out the street number would be advantageous only if you wanted to sort the addresses into numeric sequence within street, like, say, if you needed to actually visit them yourself



r937.com | rudy.ca

 

[scorpio66]

Address TEXT

;-)

 

[SQLSister]

I'm with Denny except we have three address lines and Country. Oh and we call it postal code not zip becasue we store some international stuff as well.

The other method you described is very difficult to handle in practice as not all addreses are formatted that way. It's even further complicated by the fact that you might actually have a directional as a street name (south st.) and some rural areas have very differnt ways of handling the address. And then there are the post office box type of addresses.

Questions about posting. See faq183-874

 

[LNBruno]

Keep it as simple as possible, but no simpler.

;-)

< M!ke >