Hi All

I'm thinking of building a NAS from an old computer and putting the Kexi Program (and Data) onto this.
Has anyone done this yet and tried it out? What I'm wanting to do is store all the Data on the NAS and let two different users to access it. Will Kexi work like this and at what level does it 'lock'. ie If it locks at the Database level this would not work as only one user at a time would be able to access it. If it locks at the Record level then only the record being worked on by one user would be locked to the second user. This would be what I'm looking for.

Any information, suggestions or pointers would be appreciated.

Thanks a lot

Hi Ian
My recommendation would be to use MySQL or PostgreSQL database for that with Kexi. SQLite is not (and will not be) recommended for universal, concurrent multi-user support, to avoid replicating design issues of shared file formats of MS Accessor LibreOffice Base. That's just not a scope for SQLite. After all if you have server that's more than a file server, why not to use it.

User-friendly NAS solutions like Synology (that I also use), that often offer much more than NAS functionality these days, make installation and updating of database server software available with a few clicks. That said, ordinary Linux computer can also work for local network, albeit with slightly more effort at least initially. Kexi can transparently use any database MySQL/PostgreSQL server accessible, local or remote (version 2 also had official Sybase/MSSQL support which would come back later).

Please note that currently Kexi requires all users to have access to the database server of choice (database server, not computer account), so "application server" architecture is not (yet) supported. The access can (or even should) be non-admin. Database creation rights are not required for users that will just access existing database(s). Similarly some user can have read-only assigned. This way access control can be performed according to your requirements. To control permissions and roles, or dropping unneeded databases, administration tools dedicated for your database of choice should be used. Administering functionality is not (yet) part of Kexi. Creation of databases themselves should be performed via Kexi though, existing databases created elsewhere are currently not accessible for Kexi without complex efforts (scripts) in a way other than importing them into Kexi-friendly format (even within a single server). Wish for overcoming that exists: https://bugs.kde.org/show_bug.cgi?id=380088.

Feel free to request more information.

Thanks Jaroslaw (Dziękuję)

That helps - If I understand what you say to get a central NAS device to host the Database I need to convert the DB to MySQL or other Engine first.

So my question now is - Are there any Tutorials on how to do this?? I don't remember seeing any options like this in Kexi!!

I would like to set-up a NAS to act as a central Backup for the two computers here but also for the DB so that the two users can work on it separately or at the same time and there is no need to keep copying and uploading between the two machine so that changes and edits are not lost.

Thanks again - appreciated.

The conversion is going to be similar to the raw/native-sqlite -> .kexi file conversion (tutorial https://userbase.kde.org/Kexi/Tutorials ... _into_Kexi or from viewtopic.php?f=220&t=139243), just here we have all the metadata already (queries, forms, reports...) so we just have to

1. export .kexi file (sqlite) to a .sql script
2. convert the .sql file to an .sql file compliant with MySQL/PostgreSQL requirements (there's no single standard)
3. import the resulting file by executing it on the MySQL/PostgreSQL server.

Knowledge for that is e.g.: https://stackoverflow.com/questions/186 ... 3-to-mysql. No special actions specific to Kexi are needed.
After a new database is on the server, you would open it with Kexi.

If you fail to do the conversion (or ask some admin to do that), if you send me the .kexi file privately I would send you an .sql file that you can import into your server as a new shiny database (with forms, etc. of course). Just please make sure you have a working server ready and let me know what it is (MySQL or PostgreSQL and what's the version).