Difference between revisions of "ClaimsCasespace"
| Line 15: | Line 15: | ||
== Steps to get to [[DoneDone]] == | == Steps to get to [[DoneDone]] == | ||
| − | * Handle casespace for namespace names. | + | * <s>Handle casespace for namespace names.</s> |
* <s>Write an efficient model method to cater for casespace and namespace issues.</s> Found another variant of this functionality but it used expensive join operation between page and au_page_lookup table. Came up with an ''efficient'' solution that does not require joins and uses sql with attributes in where clause that have index defined on them. | * <s>Write an efficient model method to cater for casespace and namespace issues.</s> Found another variant of this functionality but it used expensive join operation between page and au_page_lookup table. Came up with an ''efficient'' solution that does not require joins and uses sql with attributes in where clause that have index defined on them. | ||
* <s>Bootstrapping.</s> | * <s>Bootstrapping.</s> | ||
Revision as of 12:28, 11 February 2008
What (summary)
Make claims work with casespace
Why this is important
Claims is shaping up to be very important for us, and we need to get it working with our existing infrastructure
DoneDone
- Page.find_by_casespace(casename) works efficiently in compost (this is an ActiveRecord model level function)
- claim.pages honors casespace
- parsing claims that contain pages that DON'T yet exist creates claims_pages for them anyway, so that
- once a missing page is created (some casespace match), everything works without requiring a reparse
- All of this is well tested
Steps to get to DoneDone
-
Handle casespace for namespace names. -
Write an efficient model method to cater for casespace and namespace issues.Found another variant of this functionality but it used expensive join operation between page and au_page_lookup table. Came up with an efficient solution that does not require joins and uses sql with attributes in where clause that have index defined on them. -
Bootstrapping.
