PostgreSql installation problems

Sorry for the delayed response. We're planning a new patch release, due out late this week (if all goes well). That release will have our initial Postgres support. There will be more fixes from what we originally supplied to you, and we'll be going over the change you noted above. At that point, Postgres will likely still have some issues, but we'll be continuing to iron them out.

The release will also have some other minor fixes for issues that have arisen since the 5.2.1 release.

Can you confirm that I'm doing nothing wrong that might have an impact on other parts of the module? I see that, when I log in, the log out button works just fine

That getLoginRedirect code does 1 SQL query (which looks correct visually, but may have problems in Postgres when run) to check if the redirection URL is to a registered page. If so, we redirect the user to the home page on logout (so that they don't go to an ugly Joomla "You must login screen" right after they try to logout.

Commenting that out should cause problems... the user will just always be redirected to the home page or current page. If you're not experiencing any issues with it commented out, you should be fine.

I hope that helps, and thanks for the feedback!
Alex

We've been trying to recreate the following error, but haven't been able to:Are you still seeing that somewhere? If so, can you give any details of when?

As for the BIGINT conversion, we've already made a few changes to that block to make it compatible with both Postgres and MySQL. The conversion definitely should use BIGINT, but it's a conversion from a row that's already BIGINT, not VARCHAR(40). Not sure where you saw that..

Again, these updates will be in the v5.2.2 release, expected on Friday. I still don't think everything will be 100% perfect, but hopefully things will go pretty smoothly with Postgres at that time.

Thanks,
Alex

Ahh.. Silly me. Forgot what our own query was doing.

Either way, that portion of the query is actually removed in the v5.2.2 release as it's not necessary to do on the front-end like we're doing there. We've limited it only to the admin area, which is done in a different part of the code (and updated appropriately).

As for the one note (in your email) about our limit clause being wrong.. you're correct, it's wrong. However, your solution wasn't the right one either (though it makes the query work). You removed the offset parameter entirely, which means pagination wouldn't work on your site (the first page would always be shown). We updated that query to:

$query .= ' LIMIT ' . $limit . ' OFFSET ' . $limitstart;

That's a MySQL/Postgres compatible way of specifying a limit with offset, just so you know. That will, obviously, be in the v5.2.2 release as well.

Thanks for all your feedback. Just so you know, I just added 3 months to your subscription. We know you ran into some issues, and were a bit of a guinea pig. I'm sure there will be more problems you run into with Postgres support, and we'd love to keep working with you to make our support for it even better.

Alex

Hey there, one final note I wanted to get to you before we release v5.2.2 (hopefully today, but may not be until this weekend/Monday). There's one issue with Postgres that we couldn't work around in this release. When you upgrade, please do *not* uninstall JFBConnect first. Normally, that's not a problem, but for Postgres it causes a few issues right now.

Thanks again for your patience, and I hope 5.2.2 goes smoothly for you.

Alex