- air
- ajax
- algorithm
- apple
- bitbucket
- braintapper_exchange
- charts
- chumby
- codeigniter
- cognos
- complexity
- crashplan
- crosstab
- dash
- dashboard
- date
- dbvisualizer
- decisions
- dimension
- dogfood
- dona_wong
- dropbox
- edward_tufte
- extension
- feature_checklists
- feature_excellence
- filemaker
- firefox
- firewall
- flot
- flowing_data
- fogbugz
- football
- free
- freenas
- freshbooks
- git
- github
- gm
- google_charts
- iPad
- javascript
- jdbc
- jedox
- mac
- macbook
- maps
- marsedit
- mercurial
- metaweblog
- metrics
- microstrategy
- monowall
- moo
- nathan_yau
- news
- nosql
- open_source
- palo
- pentaho
- pfsense
- printing
- programmers_interfaces
- rapidweaver
- regex
- regexr
- rest
- safari
- smoothwall
- sony
- sqlpower
- stackoverflow
- statistics
- stephen_few
- svg
- tablet
- ticket_agent
- time_machine
- tip
- tm1
- transformer
- trick
- typographic grid
- usability
- visualization
- vmware
- w3c
- web
- wiki
- wikkawiki
- work_management
- wsj
Just a quick post about what type of file you should use when modeling Cognos Transformer cubes. I know the old school thinking for Windows based Transformer users was to use PYI or PYJ, but here are some reasons why I think you should use MDL instead.
- The performance gap between cube builds using PY* and MDL has narrowed significantly over the years.
- Ever get a corrupted PY* file? 'nuff said.
- MDL is a pure text format. That makes diff comparison easy when you are using source control or a tool like WinMerge
- MDL files now contain encrypted user information.
- MDL files are cross platform.
- MDL's can be parsed using a tool like Pentaho to create cube model documentation (assuming you have good habits and documented everything within the model).
- Remember the fiasco when Transformer moved to PYJ and you couldn't load a PYI? Well I do.
Just my two cents. Your mileage may vary.
