# Python List Comprehensions Help

**URL:** <https://forum.inductiveautomation.com/t/python-list-comprehensions-help/56621>\
**Category:** Ignition\
**Created:** [February 28, 2022, 3:12pm UTC](https://forum.inductiveautomation.com/t/python-list-comprehensions-help/56621 "2022-02-28T15:12:54Z")\
**Posts on this page:** 1\
**Showing post:** 59

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [March 11, 2022, 7:58pm UTC](https://forum.inductiveautomation.com/t/python-list-comprehensions-help/56621/59 "2022-03-11T19:58:27Z")

</div>

The answer, as with most things, is ‘it depends’. 🙂

In my particular application, the bom info for a production order comes from a file. Since my lookups are defined in a dictionary, I don’t have the round trip to the db. Until model year changes, it’s relatively unchanging.

That said, I also use dictionaries to manipulate datasets. You’ll notice I have a lot of [such posts](https://forum.inductiveautomation.com/t/how-to-query-data-from-two-database-peoplesoft-and-microsoft-sql-into-one-power-table/25974/7) on here.  
Joins on db tables are great and useful and are more efficient if they are in the same data source, but if you need to use datasets from two different sources, you’re hosed.

I find that db people will tend to do more with joins and stored procedures, and programmers will tend to do more through scripting.

---

_[View the full topic](https://forum.inductiveautomation.com/t/python-list-comprehensions-help/56621)._
