---
title: "Comment by Arnold Holm on \"How to Build a Python Data Bridge for MetaTrader 5 and PostgreSQL\" | Hashnode"
description: "Useful small bridge example. Two tests I'd add before using it across accounts: (1) give two servers the same numeric login and confirm the rows stay separate,"
url: "https://hashnode.com/posts/how-to-build-a-python-data-bridge-for-metatrader-5-and-postgresql/6aa4f181f53633266c5871ca/comment/6ab6856fdc4451d151287f5f"
---

[Discussion](https://hashnode.com/posts/how-to-build-a-python-data-bridge-for-metatrader-5-and-postgresql/6aa4f181f53633266c5871ca)

Comment [How to Build a Python Data Bridge for MetaTrader 5 and PostgreSQL](https://hashnode.com/posts/how-to-build-a-python-data-bridge-for-metatrader-5-and-postgresql/6aa4f181f53633266c5871ca)

[Arnold Holm](https://hashnode.com/@stratcorealpha)

[Sep 25](https://hashnode.com/posts/how-to-build-a-python-data-bridge-for-metatrader-5-and-postgresql/6aa4f181f53633266c5871ca/comment/6ab6856fdc4451d151287f5f)

Useful small bridge example. Two tests I'd add before using it across accounts: (1) give two servers the same numeric login and confirm the rows stay separate, so the key should include server; (2) change every copied account field and confirm the conflict branch updates each one. One field in the INSERT is missing from the UPDATE. Also, a single upsert keeps only the latest snapshot, not an audit history. If compliance needs changes over time, store timestamped observations separately and reconcile gaps after a disconnect.
