# Lack of stable PostgreSQL-communication a major showstopper

**URL:** https://discourse.julialang.org/t/lack-of-stable-postgresql-communication-a-major-showstopper/6934
**Category:** Data
**Created:** [November 7, 2017, 2:07pm UTC](https://discourse.julialang.org/t/lack-of-stable-postgresql-communication-a-major-showstopper/6934 "2017-11-07T14:07:03Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![johann.spies](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/johann.spies/32/8805_2.png) [@johann.spies](https://discourse.julialang.org/u/johann.spies)
#### Post date: [November 7, 2017, 2:41pm UTC](https://discourse.julialang.org/t/lack-of-stable-postgresql-communication-a-major-showstopper/6934/6 "2017-11-07T14:41:46Z")

</div>

I can try again, but ODBC has bitten me once when it filled a DataFrame with a strange datatype that I could not figure out how to handle (see [Help needed with DataFrames and Query](https://discourse.julialang.org/t/help-needed-with-dataframes-and-query/6077)). In that case the problem was corrected when I started using PostgreSQL.jl.

---

_[View the full topic](https://discourse.julialang.org/t/lack-of-stable-postgresql-communication-a-major-showstopper/6934)._