Database choice.

#1 · June 4, 2024, 1:17 pm

Good afternoon folks.  I'm a newcomer here.
I was wondering if it was best to use mysql or sqlite for a web project.
I am trying to make a charity accounts app.  Just a journal of transactions and with a running total of each category to make a trial balance.  Eg Subscriptions total.  Electric total etc.
It's only nominal accounting.
What database would be better and any idea of script to make totals in a blank page ie report.
Thanks for any small help or tips.
Thanks.

Database,script

#2 · June 5, 2024, 1:52 pm

Quote from luishp on June 5, 2024, 1:52 pm
Good afternoon! @alanfallow Welcome to the forum. Let's explore the differences between SQLite and MySQL and how you can use VisualNEO Web with neoPhp for creating PDF reports.

SQLite vs MySQL

SQLite:

Serverless: SQLite is a serverless database, meaning it doesn’t require a separate server process. The database is stored in a single file on the disk.

Setup: Very easy to set up and requires minimal configuration. Ideal for smaller projects, development, and testing.

Performance: Generally faster for read-heavy operations and small to medium-sized applications.

Scalability: Not designed for high write loads or large-scale applications.

Use Case: Best suited for embedded applications, small websites, and projects where simplicity and ease of use are priorities.

MySQL:

Client-Server Architecture: MySQL requires a running server and communicates over network protocols.

Setup: Requires more setup and configuration compared to SQLite. Needs a running server and more administrative overhead.

Performance: Scales well with large amounts of data and high write loads. Better for complex queries and concurrent access.

Scalability: Suitable for large applications, high traffic websites, and applications requiring complex transactions.

Use Case: Ideal for medium to large-scale web applications, enterprise-level solutions, and applications requiring robust data integrity and complex querying.

Choosing Between SQLite and MySQL

For your charity accounts app, if you anticipate a moderate amount of data and simpler operations, SQLite could be a good choice due to its simplicity and ease of setup. However, if you expect to scale up in the future or require more complex transactions, MySQL might be the better option.

Creating PDF Reports with neoPhp

VisualNEO Web includes a plugin called neoPhp which can help you generate PDF reports.
There is a tutorial with a source code you can check in your "Documents\VisualNeoWeb\Sample Apps" folder:

https://visualneo.com/tutorials/neopdf

Good afternoon! @alanfallow Welcome to the forum. Let's explore the differences between SQLite and MySQL and how you can use VisualNEO Web with neoPhp for creating PDF reports.

SQLite vs MySQL

SQLite:

Serverless: SQLite is a serverless database, meaning it doesn’t require a separate server process. The database is stored in a single file on the disk.
Setup: Very easy to set up and requires minimal configuration. Ideal for smaller projects, development, and testing.
Performance: Generally faster for read-heavy operations and small to medium-sized applications.
Scalability: Not designed for high write loads or large-scale applications.
Use Case: Best suited for embedded applications, small websites, and projects where simplicity and ease of use are priorities.

MySQL:

Client-Server Architecture: MySQL requires a running server and communicates over network protocols.
Setup: Requires more setup and configuration compared to SQLite. Needs a running server and more administrative overhead.
Performance: Scales well with large amounts of data and high write loads. Better for complex queries and concurrent access.
Scalability: Suitable for large applications, high traffic websites, and applications requiring complex transactions.
Use Case: Ideal for medium to large-scale web applications, enterprise-level solutions, and applications requiring robust data integrity and complex querying.

Choosing Between SQLite and MySQL

For your charity accounts app, if you anticipate a moderate amount of data and simpler operations, SQLite could be a good choice due to its simplicity and ease of setup. However, if you expect to scale up in the future or require more complex transactions, MySQL might be the better option.

Creating PDF Reports with neoPhp

VisualNEO Web includes a plugin called neoPhp which can help you generate PDF reports.
There is a tutorial with a source code you can check in your "Documents\VisualNeoWeb\Sample Apps" folder:

https://visualneo.com/tutorials/neopdf

Vadim has reacted to this post.

#3 · June 5, 2024, 4:02 pm

Thank you so much for reply.

So sqllite just gets accesed from hosting one I upload it.

Will have a look at it later. One more thing if you can. The neomenu system how do I get that going. I see it is javascript.

I will use buttons if it's easier.

Thanks again.

#4 · June 5, 2024, 4:05 pm

Forgot to add would need to do calculations in report. So I would assume it's sql in the php accessing sqlite.

Sorry just double checking.

#5 · June 7, 2024, 11:44 am

@alanfallow, regarding neoMenu, please check this sample app (you should find the source code under my Documents folder within your own PC):
https://visualneo.com/tutorials/neomenu

So I would assume it's sql in the php accessing sqlite

Yes, if you are using neoPhp plugin you can use SQL.
Please take a look at the video tutorial in our YouTube channel for more information:
https://www.youtube.com/watch?v=jIAN5B2dSl0&list=PL0I-4WLYvbmg0uBSo6jabSg034o8_lbfx

Regards.

javadrajabihakami has reacted to this post.

Database choice. - Forum

Database choice.

SQLite vs MySQL

Choosing Between SQLite and MySQL

Creating PDF Reports with neoPhp

SQLite vs MySQL

Choosing Between SQLite and MySQL

Creating PDF Reports with neoPhp