Overflowing
- 31
- 1
I was using VB4.2, whatever the latest service release was around Sep-Nov 2013.
I never looked closely at the database structure for VB but I had to dig pretty deep into how DNN7.0 was set up, and compare it to XF1.3.x and those were somewhat similar from a table structure perspective (and on the UI as well - PMs were "threaded" rather than all individual messages)
I doubt I have a backup of my VB hanging around but I might.
XF's structure is across multiple tables as well but when you figure it out, it makes perfect sense.
The conversation master which defines/tracks quite a few things, mainly the conversation ID, title, user ID that started it, etc.
The message table holds all the individual messages and who generated them & when
the recipient table tracks who is part of the conversation (and who has left it, in XF)
The User table seems to track most of the same info as the Recipient table plus a few other things
They are all sort of intertwined in an odd way but I'm sure there is some logical reason for it.
We had gConverter do it for us and they nailed it for super cheap. And that was for 2 generations of PMs, we had an older database that didn't convert on an upgrade and was barely still accessible.
I never looked closely at the database structure for VB but I had to dig pretty deep into how DNN7.0 was set up, and compare it to XF1.3.x and those were somewhat similar from a table structure perspective (and on the UI as well - PMs were "threaded" rather than all individual messages)
I doubt I have a backup of my VB hanging around but I might.
XF's structure is across multiple tables as well but when you figure it out, it makes perfect sense.
The conversation master which defines/tracks quite a few things, mainly the conversation ID, title, user ID that started it, etc.
The message table holds all the individual messages and who generated them & when
the recipient table tracks who is part of the conversation (and who has left it, in XF)
The User table seems to track most of the same info as the Recipient table plus a few other things
They are all sort of intertwined in an odd way but I'm sure there is some logical reason for it.
We had gConverter do it for us and they nailed it for super cheap. And that was for 2 generations of PMs, we had an older database that didn't convert on an upgrade and was barely still accessible.