3 years ago
#11
It works! The error was not clear. Just copy over all the trongate tables from mysql to the mysqlite db. The errors will dissapear.
3 years ago
#12
Hi Andrew, you may want to create a new thread unless the below works for you.
Good to see you got it working too :) this is my solution.
database.php - added constant 'DB_TYPE':
The top part of Model.php that now supports the above database drivers:
Cheers,
Si
Good to see you got it working too :) this is my solution.
database.php - added constant 'DB_TYPE':
The top part of Model.php that now supports the above database drivers:
Cheers,
Si
3 years ago
#13
*** UPDATE
The previous solution I implemented appears to be functioning well with MySQL, MariaDB, PostgreSQL, and SQLite, allowing for basic CRUD operations with these database driver types.
However, there are compatibility issues with certain SQL calls within the framework, which were originally designed for MySQL. Implementing these calls would likely cause more problems than benefits. Therefore, I strongly advise against merging this solution into Trongate. While it is technically feasible, the potential advantages may not outweigh the effort for the limited number of users who would benefit from it.
Last night, I dedicated several hours to enabling SQLite integration with the API Explorer, and it proved to be a straightforward process that required only a few modifications. However, PostgreSQL poses a different challenge altogether, as it presents numerous incompatibilities with MySQL. Consequently, incorporating PostgreSQL into the framework would be ill-advised.
The previous solution I implemented appears to be functioning well with MySQL, MariaDB, PostgreSQL, and SQLite, allowing for basic CRUD operations with these database driver types.
However, there are compatibility issues with certain SQL calls within the framework, which were originally designed for MySQL. Implementing these calls would likely cause more problems than benefits. Therefore, I strongly advise against merging this solution into Trongate. While it is technically feasible, the potential advantages may not outweigh the effort for the limited number of users who would benefit from it.
Last night, I dedicated several hours to enabling SQLite integration with the API Explorer, and it proved to be a straightforward process that required only a few modifications. However, PostgreSQL poses a different challenge altogether, as it presents numerous incompatibilities with MySQL. Consequently, incorporating PostgreSQL into the framework would be ill-advised.
3 years ago
#14
Hello
There are some things that differ between database managers, for example in postgresql the operator as is case sensitive.
Thanks.
There are some things that differ between database managers, for example in postgresql the operator as is case sensitive.
Thanks.
2 years ago
#15
It's such a pity! I initially found a framework that could replace Laravel and CodeIgniter, but due to the company's requirement to use PostgreSQL, it seems I'll have to reluctantly give it up :(
2 years ago
#16
Xavier,
I am so tired of seeing snotty-nosed lazy devs bitch and moan that they need x or y.
While I get your frustration with 'your' PostgreSQL requirement, but laying blame and quitting won't solve anything.
I have watched Trongate evolve from day one. Witnessed over four years of continual hard work and dedication from David to give us a FREE framework so feature-rich and far removed from the bloated rubbish that is out there.
It's crucial to recognise that a framework's strength extends beyond its author's capabilities; it thrives on the collaborative efforts of its community. Trongate, like any open-source project, flourishes when users actively contribute and share insights.
As users, we wield significant influence in shaping the framework's evolution. Encountering limitations or specific requirements is not an excuse to passively watch; it's an opportunity for the community to unite and craft innovative solutions.
Let's break free from the mindset of relying solely on DC to handle everything. Your contributions, along with others in the community, have the power to profoundly impact the framework's versatility.
Step up and actively shape Trongate's future!
Best,
Simon
I am so tired of seeing snotty-nosed lazy devs bitch and moan that they need x or y.
While I get your frustration with 'your' PostgreSQL requirement, but laying blame and quitting won't solve anything.
I have watched Trongate evolve from day one. Witnessed over four years of continual hard work and dedication from David to give us a FREE framework so feature-rich and far removed from the bloated rubbish that is out there.
It's crucial to recognise that a framework's strength extends beyond its author's capabilities; it thrives on the collaborative efforts of its community. Trongate, like any open-source project, flourishes when users actively contribute and share insights.
As users, we wield significant influence in shaping the framework's evolution. Encountering limitations or specific requirements is not an excuse to passively watch; it's an opportunity for the community to unite and craft innovative solutions.
Let's break free from the mindset of relying solely on DC to handle everything. Your contributions, along with others in the community, have the power to profoundly impact the framework's versatility.
Step up and actively shape Trongate's future!
Best,
Simon