Which database

[Oliver901]

Which database works best with LiveCode?

[Klaus]

LC comes with a build-in SQLite engine, so this might be the best option for a single user DB.
However LC supports MySQL, postgreSQL and many other database engines.

[Oliver901]

LC comes with a build-in SQLite engine, so this might be the best option for a single user DB.
However LC supports MySQL, postgreSQL and many other database engines.

Non-SQL database are suitable?

[Klaus]

Sorry, no idea...

[stam]

Non-SQL database are suitable?

Hi Oliver,
LiveCode has drivers for SQLite, MySQL, PostgreSQL and ODBC. I think it's possible to use MariaDB as well and Valentina provides drivers if you want to see Valentina server instead...

noSQL databases are by-and-large online entities and you would usually communicate with them via REST APIs, which is eminently feasible in LC...

a liveCode specific noSQL database you can use right away is LiveCloud (https://livecloud.io - there is a free tier you can use) - but any database that provides a REST API is fully usable.

[FourthWorld]

LC comes with a build-in SQLite engine, so this might be the best option for a single user DB.
However LC supports MySQL, postgreSQL and many other database engines.

Non-SQL database are suitable?

There is a CouchDB library available in these forums.
viewtopic.php?f=12&t=24925

And just about anything with a REST API can be used.

The question is better approached by determining the type of database that best fits your application needs, and then determining how to use it from LC.

[Oliver901]

Thank you all for the help

[markwilliams21]

Hi there,

Choosing the right database for your LiveCode project depends on several factors, including your specific requirements, the scale of your application, and your familiarity with different database systems. Here are some options you might consider:

SQLite:

Pros: Lightweight, easy to set up, and ideal for single-user applications or small projects.
Cons: Not designed for high-concurrency or large-scale applications.
Integration: LiveCode has built-in support for SQLite, making it easy to use.
MySQL/MariaDB:

Pros: Robust, widely used, and suitable for larger applications with multiple users.
Cons: Requires more setup and maintenance compared to SQLite.
Integration: You can use LiveCode’s revDB library to connect to MySQL/MariaDB databases.
PostgreSQL:

Pros: Highly extensible, supports complex queries, and has strong community support.
Cons: Can be more complex to set up and manage.
Integration: LiveCode also supports PostgreSQL through the revDB library.
Salesforce:

Pros: Powerful CRM features, cloud-based, and excellent for applications that require advanced customer relationship management.
Cons: Typically used for specific use cases and can be more expensive.
Integration: You can interact with salesforce database using LiveCode’s HTTP commands and the Salesforce REST API.
Others:

If you need NoSQL databases like MongoDB or need to interact with other types of data stores, LiveCode can connect to these using APIs and custom scripts.
Recommendation:

For simple, local storage needs, SQLite is often sufficient and very easy to use with LiveCode.
For more complex, multi-user applications, MySQL or PostgreSQL are better choices.
If your project heavily relies on CRM functionalities, consider integrating with Salesforce.
Ultimately, the best database for your project will depend on your specific needs and constraints. Feel free to provide more details about your project requirements if you need a more tailored recommendation.

I hope this helps! Let me know if you have any other questions or need further assistance.

[Klaus]

Dear AI,

thank you very much for this elaborate explanation!


Best

Klaus

[jacque]

I'm waiting for one AI post to answer another. Kind of like that time someone engaged Siri to talk to Google Assistant.

[SparkOut]

I may be imagining but I think that's already happened here sometime, but then I don't have a reliable memory.