For priority I'd suggest adding a column called priority (typically int(3) integer between 0 and 999) and doing ORDER by that column.
Do not forget to add an index as well or it might slow things down! 2013/11/12 ha...@aeon.pk <ha...@aeon.pk>: > Hi, > > Many thanks. I tried and tested it. It works fine for small chunks of data > (I can see SMS going out of bbox in a sequence they were entered in send_sms > table). However, for large amount of data (e.g. I sent a bulk of 20k SMS via > SQLBOX), it does not follow the same rule. Is it bearerbox which shuffles > the order of the SMS present in its buffer (not SQLBOX)? Any > thoughts/experiences? > > Is there any parameter tweak in send_sms by which I could raise the priority > of some SMS higher than others? > > Regards, > > > > On Mon, Nov 11, 2013 at 9:23 PM, spameden <spame...@gmail.com> wrote: >> >> Yes you can do this. >> >> Just alter gw/mysql_sqlbox.h and edit >> >> #define SQLBOX_MYSQL_SELECT_QUERY >> >> add there ORDER by sql_id ASC :) >> >> 2013/11/11 ha...@aeon.pk <ha...@aeon.pk>: >> > Hi, >> > >> > Does SQLBOX work in LIFO or FIFO order? For me, it's working as LIFO >> > which >> > is bad if I intend to send sequential message (message 1 needs to go >> > first, >> > but since message 2 comes later, it goes out first). >> > >> > Is there a way to make it operate in FIFO sequence, like ID'ing the >> > messages >> > or something? >> > >> > Regards, >> > Hamza > >
