INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Best Practice? Custom Field vs. Expression Column  (Read 749 times)

Ferdi

  • World Citizen
  • ***
  • Posts: 195
Best Practice? Custom Field vs. Expression Column
« on: January 28, 2019, 11:56:04 pm »

To manage my library I have created various custom fields. Some have to be manually filled (e.g., 'Rating on Pitchfork', 'Sync to Sonos'), others are calculated.

I have recently read some posts that address certain situation by creating expression columns. And now I am wondering what the cons and pros are!
For example, I have a calculated field 'Year - Album' (to list all albums of an artist in chronological order, with both release year and name of album in one field). Instead, I could create an expression column, but what value would that bring? Fields are re-usable.

Any thoughts on this topic at all?
Logged

Hendrik

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 10923
Re: Best Practice? Custom Field vs. Expression Column
« Reply #1 on: January 29, 2019, 03:13:53 am »

Custom expression-based fields are automatically available everywhere. An Expression column is limited to the view you created it in. It greatly depends on what you are trying to solve here.
Show a certain computed value in one view only? Use an expression column.
Show such a value in various views, or use it in other expressions further? Use a field.
Logged
~ nevcairiel
~ Author of LAV Filters
Pages: [1]   Go Up