Rewrite serializable to have field level granularity

Represent serializable objects in a digraph, and as a result made most
object relationships implicitly defined, and use the graph to trace
references between objects to determine relationships. Edges may
also be marked as having a dependency of the object they point to,
which allows for automatic cleanup and deletion of most objects when
no longer needed.

Additionally, this allows not having to require in-memory copies of
everything when using external databases. db_sql has been rewritten
for this and now always requires a database to function. db_sql with
MySQL now requires InnoDB to make use of transactions and foreign
key constraints.

1 files changed, 2 insertions, 2 deletions

diff --git a/modules/extra/m_sql_log.cpp b/modules/extra/m_sql_log.cpp
index 496ecb5e6..2be893cba 100644
--- a/modules/extra/m_sql_log.cpp
+++ b/modules/extra/m_sql_log.cpp
@@ -99,9 +99,9 @@ class SQLLog : public Module
 		}
 
 		insert.SetValue("user", l->u ? l->u->nick : "");
-		insert.SetValue("acc", l->nc ? l->nc->display : "");
+		insert.SetValue("acc", l->nc ? l->nc->GetDisplay() : "");
 		insert.SetValue("command", l->c ? l->c->name : "");
-		insert.SetValue("channel", l->ci ? l->ci->name : "");
+		insert.SetValue("channel", l->ci ? l->ci->GetName() : "");
 		insert.SetValue("msg", msg);
 
 		SQL->Run(NULL, insert);