I need a mobile SQL

Solarion

Solarion

Honorary Master
Joined
Nov 14, 2012
Messages
28,048
Reaction score
17,803
I'm looking for something I can use because the one client does not want to install SQL server. It's a fairly small app itself only holds about 12 users information with time cards for each person. What can I use?
 
Why not a flat file?

This the application doesn't seem to heavy?
 
If you need a database on the mobile device, then go for SQLite. If you need something server side, then use MySQL or PostgreSQL. You mentioned running reports, which sounds like more server side.
 
If it is a proper RDBMS you need server-side then yes, SQLite is not really that. I do love it however because I hate databases with their referential integrity and stront-procs. SQLite has none of that. Sure you can setup PKs and FKs but whether referential integrity is enforced is up to you. Or at least that is how it was last time I used it.
 
+1 for Sqlite

BUT, if the project needs a SQL server (because of concurrent connection issues etc... although you need a substantial load for this to become an issue i think) and he doesn't want to install and maintain a sql server, there are one click installation servers available like DigitalOcean etc but that carries cost.

Reckon go with SQLite but make sure you interface the data layer so you can swap it out for a DB server if that day should come.
 
XXAMP/ WAMP or varients, but not for cell dev.
 
Solarion said:
I'm looking for something I can use because the one client does not want to install SQL server. It's a fairly small app itself only holds about 12 users information with time cards for each person. What can I use?
Click to expand...

Is there a reason your client doesn't want to install SQL Server?
 
gkm said:
If you need a database on the mobile device, then go for SQLite. If you need something server side, then use MySQL or PostgreSQL. You mentioned running reports, which sounds like more server side.
Click to expand...

Rather go for MariaDB. Original developers of MySQL , and with an open source license. Rumors are Oracle could change MySQL licensing and you'd have to start paying license fees soon.
 
Unfortunately I can't +1 sqlite because the OP didn't specify the use-case. If the "mobile" needs to sync to some centralized database somewhere so that other "mobile" users can see/access the updated data and pull reports from everyone concerned, then sqlite won't fit in well because it's usually tied to the device that's not syncing to a central db at all.

They also failed to specify if this is a native app on mobile devices, or just a responsive HTML5 implementation. When working with HTML5, you have several storage options, but again, if the client, at any point in time wants to see what Sales Rep 1 is doing, there needs to be a central database to store this in.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X