Erm.
I've seen some weird responses to this. Yes, you can do this.
First -- get the data into a usable format. Then, put it into a usable
format (eg, timestamp for datetime field).
Read up on how mysql interprets date/time data on fields. And, create a
new timestamp or date field.
Then, do
Hey Morgan,
Thanks for the tip. Might come in handy.
But, I'm positive it's not a disconnect / reconnect thing. Or, at least
not one affected by that timeout.
I can do a watch ls -lh in the binlog dir, and see the relay log
increasing in size by a M every 4 or 5 seconds or so. About
200kbyt
I should add that I've turned the SQL thread off, it makes no difference
from what I can see...
On Fri, 20 Jan 2017 10:31:38 -0500
Brad Barnett wrote:
>
>
>
> On Fri, 20 Jan 2017 10:30:09 -0500
> Brad Barnett wrote:
>
> >
> >
> > Hey Morgan,
&g
Hey all,
I have a weird issue.
MySQL community edition 5.6.29, running Linux.
Binlogs never seem to get caught up on slaves.
I've done all I can, to validate that this isn't network or disk related.
Disk tests (using iostat and other methods) show lots of bandwidth left
on the slave and ma
SELECT
url,newwebsites.description,newwebsites.title,newwebsites.catid,category.fullname,MATCH
newwebsites.description AGAINST ('aliens') as GOO from newwebsites,category LEFT
JOIN userrestrictions ON userrestrictions.name REGEXP
'[[:<:]]username|GLOBALAUTHADMIN[[:>:]]' AND
newwebsites.catid=user
