Re: Varchar vs foreign key vs enumerator - table and index size

On 8/31/13 8:35 AM, Łukasz Walkowski wrote:
> 3. And this part is most interesting for me. Columns browser, eventsource, eventtype, devicetype, operatingsystem
containa small pool of strings - for example for devicetype this is set to Computer, Mobile, Tablet or Unknown. Browser
isset to normalized browser name. In every case I can store those data using one of 3 different methods: 

Sorry for the late reply... the Enova Tools project in pgFoundry has code that lets you create a "dynamic lookup table"
thatallows for easily normalizing slow-changing data. You could then put a writable view on top of that so that the app
wouldn'tknow the difference. It also has a backfill framework that would help you move data from the old table to the
newtable. 
--
Jim C. Nasby, Data Architect                       jim@nasby.net
512.569.9461 (cell)                         http://jim.nasby.net