Registered Member
|
Does anyone have a sample database here with Kexi, that already has some reports/queries/tables created in so that you can input data into the forms, in which puts the data needed into the tables, and then some queries getting the data from those tables?
I've got about minimum 10 different sites that i need to gather information on for high level purposes, such as site name, address, internet speeds, services provided, phone numbers, fax numbers, domain names, expiration dates, contract dates, etc. Thanks, |
Moderator
|
Hi
There is a Simple database we maintain that shows the use of tables, forms, reports and queries: see "Simple database" at https://userbase.kde.org/Kexi. |
Registered Member
|
Thanks for the post. A couple of questions, how do i see the relationships between the tables? Also, is there a way to somewhat take this information and easily show it securely just on my local PC in the web browser?
|
Moderator
|
Relationships between the tables: before we've had such a view in KEXI 0.x. Now it is disabled due to reliability - it was not finished. Actual state is that relationships we define in KEXI come from the column bindings in Table Designer (the combo box building blocks) and nothing else.
Relationships in queries is probably ot what you're asking for, as these are light relations at query level. We do not have database structure information exportable for now. There was a plan for project's documentation generator, it's clear how to do that but it is still waiting for sufficient funding though. We've been working on web forms too - https://community.kde.org/Kexi/Plugins/Web_Forms, it was very nice self-contained tech and it now needs maitnainer and founding. |
Moderator
|
Hi Kristpom If we're talking about database relationships (as MS Access defines them for example, IIRC), this feature isn't public yet in KEXI. A way to display such relations is to open the database (sqlite or mysql, pgsql etc.) in a software that supports such feature. However, given that foreign keys (FK) are not utilized by KEXI under the masek you won't see much. Why is that KEXI does not utilize FKs? [1] - Historical reasons in SQLite 3, see "introduced in SQLite version 3.6.19 (2009-10-14)" --> https://www.sqlite.org/foreignkeys.html. That was 5 years later than we wanted it... - DIfferences between what is meant by FK in various db backends used by KEXI (mysql, postgreSQL, SQLite...) - In short SQL hell of missing standardization There's a route to overcome the limitations in KEXI, clean things up. As with dozens of db features in KEXI. SQLite 3 now has dozens and dozens of powerful db features (originally even implicitly declared that they are too complex for SQLite). Altering table schema is one of them. Lots of that can be implemented in such projects are kickstarted. That's by the way, I hope this shows the bigger picture. [1] KEXI instead keeps metadata as documented more or less here http://kexi-project.org/wiki/wikiview/i ... lumns.html |
Registered users: Bing [Bot], Google [Bot], Sogou [Bot], Yahoo [Bot]