ERROR database: postgresql_error: ERROR: operator does not exist: ` integer #193
Comments
Hitting the same issue using latest master (that would be f9186f2). @mesteele101 can't make sense of the build numbers you're referring to, which commit would that be? |
This problem is directly related to build 337 of Barnyard2. Build 337 compiles just fine with the latest PostgreSQL source, but running Barnyard2 on a PostgreSQL server fails. If I compile 336 using the same PostgreSQL source, I have no problems running Barnyard2 and connecting to a PostgreSQL server. |
Where can build 336 be found? |
someone find the solution? I got some problem here... |
I have the solution: Edit this file before compile And replace everything Then compile it. I do not know this will be affect to another driver or not. At least it would be help in postgres. I thought this is a bug for postgres @firnsy |
fathur's solution confirmed. |
I just downloaded and the above lines to change are not in the file? Has the latest Barnyard2 been modified to include that change.
|
I have checked and it is still there... https://github.com/firnsy/barnyard2/blob/master/src/output-plugins/spo_database_cache.h |
Thanks, I was looking at something different. Is this problems specific to Barnyard2, or it the problem caused by some other application? I'm wondering why this fix has yet to be incorporated into Barnyard2? |
I think this is a bug in Barnyard2 for postgreSql database. Other applications should not affecting when compile it. |
This problem is still occurring - is this likely to be fixed any time soon? Patch below:
|
I think the merging of PR #186 on Apr 12, 2016 caused this issue. |
Commit dd441fd broke PostgreSQL support. :frown: Learned that from reading firnsy/barnyard2#193
Running build 336 just fine, compiles, and runs. Compiled build 337 with no error. After running in same enviromet as build 336 I get the below:
Moving back to 336 there is no problem...
The text was updated successfully, but these errors were encountered: