Person shipping address details should be broken out into seperate table
Bug #6495 reported by
Stuart Bishop
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Low
|
Stuart Bishop |
Bug Description
The shipping address columns should be broken out of the person table into a
new DefaultShipping
This information is large, and generally not used, so moving it to a
seperate table will significantly shrink the Person tables size speeding
things up.
affects /products/launchpad
--
Stuart Bishop <email address hidden> http://
Canonical Ltd. http://
Attachment: signature.asc
Type: application/
URL: http://
Changed in launchpad: | |
status: | Unconfirmed → Confirmed |
Changed in launchpad: | |
assignee: | nobody → stub |
Changed in launchpad: | |
importance: | Medium → Wishlist |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad-foundations: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Well, the shipping-related columns in the Person table were never
(AFAIR) actually used in our code. I see, though, that we have (on
staging) 25287 people with non-NULL shipping addresses, so I wonder how
they ended up there. Maybe it's from an early version of shipit which
used to store the shipping address in the person table instead of
shippingrequest, as it does currently.
Anyway, I think it should be ok to drop these columns from the person
table unless we plan to add a way for people to set their shipping
address on Launchpad itself, rather than on shipit.