Reply to thread

Message

<blockquote data-quote="dvdfreak" data-source="post: 165203" data-attributes="member: 21313">Lucky in a way, MP won't know how that data got in there, but it will mostly just work.&nbsp; Today.However(!), the idea is to definitely move away from stuff like this.&nbsp; I've been advocating a separate scheduling subsystem, behind a well defined service API.&nbsp; So writing directly into the database is an absolute &quot;not-done&quot; <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />&nbsp; The proper way to register a schedule then is to go through the proper channels, talk to the scheduling service and ask it to do this for you.The advantages are obvious: it is simple, and no matter what changes underneath (the database, some code, whatever), it will always remain working for you, the user of the service <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="dvdfreak, post: 165203, member: 21313"] Lucky in a way, MP won't know how that data got in there, but it will mostly just work. Today. However(!), the idea is to definitely move away from stuff like this. I've been advocating a separate scheduling subsystem, behind a well defined service API. So writing directly into the database is an absolute "not-done" ;) The proper way to register a schedule then is to go through the proper channels, talk to the scheduling service and ask it to do this for you. The advantages are obvious: it is simple, and no matter what changes underneath (the database, some code, whatever), it will always remain working for you, the user of the service :) [/QUOTE]

Verification