| Summary: | Add support for regular sqlite database files and connections to existing MySQL databases | ||
|---|---|---|---|
| Product: | [Applications] KEXI | Reporter: | Mathieu Jobin <opensource> |
| Component: | KexiDB | Assignee: | Jarosław Staniek <staniek> |
| Status: | CLOSED LATER | ||
| Severity: | wishlist | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Mathieu Jobin
2006-03-20 03:19:38 UTC
Agreed. This is called linking to external data. Planned for Kexi 1.1 but due to KDE4-related tasks it's more realistically to expect it in 2.0. well, .kexis file already link to mysql database, but won't scan for tables. kexi will only know about table created within kexi. as for sqlite, since .kexi file are native sqlite file, i wish linking would not be necessary here. but kexi would simple understand .kexi, .sqlite, .sqlite3 files as the same thing. but instead of creating empty system tables upon database creation, it would only be created once required. Like, when you create a form, a query, or something like that. and at that point, I suppose table and field list would not need to be stored in system table anymore. they could be cached i guess, but primary info would be taken from the core. well, I'm just speculating how I would like things to be. thanks, kexi is coming along very well, and I'm happy its part of the official koffice 1.5 release. thanks Planned for 2.0 version. |