# Approaches for querying the PostgreSQL?

**URL:** <https://forum.opentap.io/t/approaches-for-querying-the-postgresql/109>\
**Category:** Technical\
**Created:** [November 8, 2020, 9:43pm UTC](https://forum.opentap.io/t/approaches-for-querying-the-postgresql/109 "2020-11-08T21:43:22Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![jason.hicks](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.opentap.io/jason.hicks/32/281_2.png) [@jason.hicks](https://forum.opentap.io/u/jason.hicks)\
**Post date:** [August 15, 2021, 12:23am UTC](https://forum.opentap.io/t/approaches-for-querying-the-postgresql/109/4 "2021-08-15T00:23:44Z")

</div>

@nick1 , have you thought about creating your own ResultsListener? You then have control how the results are stored and thus queried and presented.

> [@MongoDB anyone?](https://forum.opentap.io/t/mongodb-anyone/387):
>
> @carlos.montes, thanks for suggesting this, and I will try to find the time to keep updating the topic. I initially thought of posting the ResultListener verbatim, but due to my result storage paradigm, I decided it may be better to begin with a walkthrough of sorts, to get interested readers thinking about the whole result lifecycle. I don’t want to force my opinions on anyone about how results should be stored, so it may be worth starting from the beginning to create the ResultListener from …

---

_[View the full topic](https://forum.opentap.io/t/approaches-for-querying-the-postgresql/109)._