--
--
Sie erhalten diese Nachricht, weil Sie Mitglied sind von Google
Groups-Gruppe "OpenOlat".
Für das Erstellen von Beiträgen in dieser Gruppe senden Sie eine E-Mail
an open...@googlegroups.com
Um sich von dieser Gruppe abzumelden, senden Sie eine E-Mail an
openolat+u...@googlegroups.com
Weitere Optionen finden Sie in dieser Gruppe unter
http://groups.google.com/group/openolat?hl=de
-------------------------------------------------------------------------------------------------------------------
OpenOlat - infinite learning - http://www.openolat.org
---
You received this message because you are subscribed to the Google Groups "OpenOlat" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openolat+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openolat/0aa7ca46-3482-4a37-b9af-e1b1b5216361%40googlegroups.com.
Hi P.W.Use the REST API and do not directly access the database! In any case, never directly write into the OpenOlat database schema or filesystem!The API encapsulate the data storage that is partially on the filesystem and partially in the database. Knowing the database schema does not give you a complete understanding of OpenOlat. There are crucial parts, such as the course data model, which are held as XML files on the filesystem and are not stored in the database. OpenOlat is not a frontend for a relational database model.OpenOlat can cache some objects in RAM to minimize database access. When modifying the database while OpenOlat is running you can cause data inconsistencies or in worst case corrupt the data model.To summarise: do not access the database directly unless you know exactly what you are doing. Use the REST API instead.CheersFlorian
Am 15.11.2019 um 14:30 schrieb P. W. <in...@pwiesendanger.de>:
Our general goal is to manage questions, tests, courses... in an external application and we are searching for a solution for the easiest way to manage the data and toex-/import it
On Friday, November 15, 2019 at 1:51:37 PM UTC+1, P. W. wrote:Hello,we are currently working on a project to im- and export data from OpenOLAT to an SQL database, based on exported QTI files. Do parsers for that use case already exist or what would be the easiest way to solve the conversion from QTI into a SQL database bidirectonal? We know that OO is based on a SQL database, but with direct access to the database, the access management of OO wouldn't work to only export the data that is linked to the exporting user.Also: Is there any documentation on the SQL database schemes of OO available?Best regards,P. W.--
--
Sie erhalten diese Nachricht, weil Sie Mitglied sind von Google
Groups-Gruppe "OpenOlat".
Für das Erstellen von Beiträgen in dieser Gruppe senden Sie eine E-Mail
an open...@googlegroups.com
Um sich von dieser Gruppe abzumelden, senden Sie eine E-Mail an
Weitere Optionen finden Sie in dieser Gruppe unter
http://groups.google.com/group/openolat?hl=de
-------------------------------------------------------------------------------------------------------------------
OpenOlat - infinite learning - http://www.openolat.org
---
You received this message because you are subscribed to the Google Groups "OpenOlat" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openolat/0aa7ca46-3482-4a37-b9af-e1b1b5216361%40googlegroups.com.
Weitere Optionen finden Sie in dieser Gruppe unter
http://groups.google.com/group/openolat?hl=de
-------------------------------------------------------------------------------------------------------------------
OpenOlat - infinite learning - http://www.openolat.org
---
You received this message because you are subscribed to the Google Groups "OpenOlat" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openolat+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openolat/b5c78a17-03c6-4840-952a-172e42606f49%40googlegroups.com.