InFailedSqlTransaction

lshrep · April 21, 2023, 6:58pm

Hi all,
I have setup an instance of Frappe (v14.30.0) on Ubuntu 22.04, with a Cloud SQL Postgres as the database.
The setup is working fine, and I installed ERPnext (v14.18.3) on my site. However when I try to login to the Desk, I get this very strange behavior.

At first there is below error when I enter my credentials (and it happens every single time) :

And then when I refresh the page I am able to get to the Home page of ERPnext.
I can add the full stack trace if needed.

Can someone please help decrypt what is going on ? I do not understand why such a behavior.

zedomaru · April 23, 2024, 11:11am

Hi there, do you figure this out? I’m facing the same issue.

lshrep · August 12, 2024, 11:37pm

No, but I have been searching lately again and it seems like Frappe is compatible with Postgres, but not ERPnext. So if you only want to do custom development maybe it should work. Check out these github issues for more info :

github.com/frappe/erpnext

Postgres support for ERPNext

opened 04:32AM - 18 Jan 21 UTC

rmehta

feature-request valid

Frappe Framework has support for both MariaDB and Postgres. ERPNext does not hav…e support for Postgres. While queries are mostly similar, there are 1300 SQL queries that need to be verified and checked. Thankfully we have unit-tests. Steps: 1. Setup tests for postgres (similar to Frappe Framework) 2. Makes sure the tests pass for all queries If there are problems in certain SQL queries: 1. Use the ORM 2. Rewrite the query so that it will work for both databases 3. Use `frappe.db.multi_sql` to write separate queries for each platform (for complex joins)

github.com/frappe/frappe

Megaissue for tracking stable postgres support

opened 06:46AM - 09 Jul 23 UTC

ankush

postgres

Postgres support has been there in beta since LONG time now. ERPNext postgres su…pport is in demand too for quite some time. Creating this issue to breakdown the problem and address them one at a time before framework can have prod ready support for production. Tasks: - [ ] Address all issues labelled `postgres` - https://github.com/frappe/frappe/issues?q=is%3Aissue+is%3Aopen+postgres+label%3Apostgres - [ ] Fix `type_map` mismatches between MariaDB and Postgres. Types used in both DB should be similar. - [ ] Run patch test, UI tests on Postgres DB too but in a limited/sampling basis to avoid CI load. - [ ] Find all tests that are skipped for postgres with `@run_only_if(db_type_is.MARIADB)`, add support for those features and run those tests for postgres too. - [ ] Do first cut profiling of things using Postgres. Basically audit of indexes and schema parity with mariadb version. - [ ] Review `schema.py` for both files. Add tests for ALL behaviour in this file and make sure both DB have equivalent support. This primarily includes creation of table and altering table after schema is changed. --- To anyone willing to help: - please keep your PRs small and reviewable. One giant PR is unlikely to get merged. - Add tests for every feature, behaviour, bug. DB interface is most crucial part of Framework and needs to have near 100% coverage.