Kexi/Integration/Bibliographic Database: Difference between revisions
< Kexi | Integration
No edit summary |
No edit summary |
||
| Line 12: | Line 12: | ||
**As a result, data will be cached on retrieval, allowing proper editing and filtering filtering | **As a result, data will be cached on retrieval, allowing proper editing and filtering filtering | ||
**The data will be put into a table model (Qt Model/View) as needed by Words' GUI | **The data will be put into a table model (Qt Model/View) as needed by Words' GUI | ||
==Issues== | |||
Following issues should be addressed: | |||
* all columns in the bibref table are of Text type | |||
* why there is one table per db? | |||
Revision as of 15:30, 17 April 2013
Words' Bibliographic Database - effort/code sharing with Kexi and possible integration with Kexi.
- Initial discussion on IRC
- Possibly two-way; as a start, in Words
- CalligraDB is a lib moved in 2.6.0 from KexiDB to libs/ in order to enable reuse by Calligra apps, details at libCalligraDB
- People involved: jstaniek (CalligraDB maintenance and adaptation for biblio), smitpatel (biblio), boemann (Words maintainer)
- Only minimal changes have been made to KexiDB
- Words 2.5 used QtSql lib
- Words 2.6.0 switched to CalligraDB
- Plans for 2.6.2: fix data very inefficient way of data retrieval (O(n^2) CPU cost)
- To do so, some code have to be moved from Kexi, as agreed with smitpatel
- As a result, data will be cached on retrieval, allowing proper editing and filtering filtering
- The data will be put into a table model (Qt Model/View) as needed by Words' GUI
Issues
Following issues should be addressed:
- all columns in the bibref table are of Text type
- why there is one table per db?