Kodi Community Forum
New DB Structure for all libraries + DBs [update 2015 06 13 / Released SQL 1.3] - Printable Version

+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Development (https://forum.kodi.tv/forumdisplay.php?fid=32)
+--- Forum: Kodi Application (https://forum.kodi.tv/forumdisplay.php?fid=93)
+--- Thread: New DB Structure for all libraries + DBs [update 2015 06 13 / Released SQL 1.3] (/showthread.php?tid=200911)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20


RE: New DB Structure for all libraries + DBs [update 2015 06 13 / Released SQL 1.3] - m.savazzi - 2016-01-18

(2016-01-17, 17:49)xnappo Wrote: In Emby for Kodi - we don't take override the DB, we just sync the Emby DB to the Kodi DB. So we are overriding the scraper, not the db. The complexity of the current DB made doing this difficult (mostly the way interrelated items work on the TV side).

Of course we are watching this thread closely because it will be a lot of work for us if the Kodi DB changes Smile

Hopefully it will make your life much easier Smile


RE: New DB Structure for all libraries + DBs [update 2015 06 13 / Released SQL 1.3] - xnappo - 2016-01-18

(2016-01-18, 20:30)m.savazzi Wrote:
(2016-01-17, 17:49)xnappo Wrote: In Emby for Kodi - we don't take override the DB, we just sync the Emby DB to the Kodi DB. So we are overriding the scraper, not the db. The complexity of the current DB made doing this difficult (mostly the way interrelated items work on the TV side).

Of course we are watching this thread closely because it will be a lot of work for us if the Kodi DB changes Smile

Hopefully it will make your life much easier Smile

Longer term, yes.

Also when we looked into why JSON-RPC was slow we got to the point where it appeared the entanglement of the scraper and DB code was a big part of the problem - so hopefully with this refactor we can fix up JSON-RPC so we aren't being mavericks anymore.

xnappo


RE: New DB Structure for all libraries + DBs [update 2015 06 13 / Released SQL 1.3] - bigbig6 - 2016-04-11

Hello,


Is there any news about this subject?

regards


RE: New DB Structure for all libraries + DBs [update 2015 06 13 / Released SQL 1.3] - marantz - 2016-07-01

waiting as well... Smile


RE: New DB Structure for all libraries + DBs [update 2015 06 13 / Released SQL 1.3] - bigbig6 - 2017-07-27

Hello,

is this subject completely abandonned?

Regards,

Big


RE: New DB Structure for all libraries + DBs [update 2015 06 13 / Released SQL 1.3] - spcano01 - 2017-07-27

I really hope not...my DB is very large and getting unwieldy.


RE: New DB Structure for all libraries + DBs [update 2015 06 13 / Released SQL 1.3] - da-anda - 2017-07-28

devs are currently working on replacing our SQL layer with something object oriented. After this is done, we can think about switching over to a new DB schema.


RE: New DB Structure for all libraries + DBs [update 2015 06 13 / Released SQL 1.3] - bigbig6 - 2017-07-28

Ok,

Thanks for the news

Seems to be logical in that way...

Regards,

Big


RE: New DB Structure for all libraries + DBs [update 2015 06 13 / Released SQL 1.3] - Tolriq - 2017-07-28

Making the tool before knowing what you want to build may not sound that logical Wink

But at least it's a step forward.


RE: New DB Structure for all libraries + DBs [update 2015 06 13 / Released SQL 1.3] - garbear - 2017-07-28

(2017-07-28, 17:15)Tolriq Wrote: Making the tool before knowing what you want to build may not sound that logical Wink

True, but the DB refactor has to come first. We can't change two things at once, and the current system won't support a large scale schema change. Once the new ORM is in place, it'll be possible to adopt a new schema.

The ODB work has a feature branch in our repo: https://github.com/xbmc/xbmc/tree/feature_odb


RE: New DB Structure for all libraries + DBs [update 2015 06 13 / Released SQL 1.3] - Tolriq - 2017-07-28

Yes I've seen it already Wink

The main issues actually are tied to the fact that many things are done at Kodi level, and that many things are get via new queries and not on the first one. (Not speaking about the schema of course)

If the target is now known, the tool may in the end not fit those needs and while it will be refactored the target will still be unreachable. And many ORM are not smart about 1-n n-n relationship and needs to be carefully chosen Wink

Knowing the target shows the path. Changing a shovel for a bulldozer looks cool, but in some cases the bulldozer can't pass between the houses Wink

Disclaimer I have not actually checked what ODB offers and hope it will be the right tool.