- This topic has 1 reply, 2 voices, and was last updated 6 years, 5 months ago by .
Viewing 2 posts - 1 through 2 (of 2 total)
Viewing 2 posts - 1 through 2 (of 2 total)
- The forum ‘Internals & Enhancements’ is closed to new topics and replies.
Integrated Application Platform
Integrated Application Platform › Forums › Internals & Enhancements › HttpPostQueue – Enhancement
It was in the todo list it looked simple enough for me to fix. Code below.
Class – HttpPostQueue
ensureQueueTable()
{
// NOTE The queue table is only created once
if TableExists?(.QueueTableName) is false
{
Database(‘ensure ‘ $ .QueueTableName $ .QueueTableSchema)
}
}
Thanks Jason. Sorry for the slow reply – my email notifications seem to not be working.
Unfortunately, that’s not what the comment meant.
Database ensure internally does a check if the table schema already matches.
What we really want to avoid is doing an extra client-server database request every time, even though 99.99% of the time it’s unnecessary. (Although in the big picture this probably isn’t that big a deal.)
The question then becomes, who is responsible for creating the table? Maybe you just make ensureQueue public and leave it up to the application code to create it at some point.