Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1221464" data-attributes="member: 82144"><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite24" alt="(y)" title="Thumbs Up&nbsp; &nbsp; (y)" loading="lazy" data-shortname="(y)" />Oh, for sure!Please don't get me wrong.I really appreciate you reporting it. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite24" alt="(y)" title="Thumbs Up&nbsp; &nbsp; (y)" loading="lazy" data-shortname="(y)" />On this occasion I think the log entry being an error is a bit misleading (sorry). As long there's nothing else going on in connection with it I think we can safely leave it. The main reason I'm not going further and trying to eliminate or downgrade the log entry to avoid further/future misunderstanding is that the entry is from the database level and TVE 3.5 completely replaces the database access layer.</blockquote>

[QUOTE="mm1352000, post: 1221464, member: 82144"] (y) Oh, for sure! Please don't get me wrong. I really appreciate you reporting it. (y) On this occasion I think the log entry being an error is a bit misleading (sorry). As long there's nothing else going on in connection with it I think we can safely leave it. The main reason I'm not going further and trying to eliminate or downgrade the log entry to avoid further/future misunderstanding is that the entry is from the database level and TVE 3.5 completely replaces the database access layer. [/QUOTE]

Verification