reading the binlog, is the gtid on the record available? about go-mysql

[glycerine]

With mysqlbinlog --hexdump I can see that there are SET @@SESSION.GTID_NEXT records in the binlog, I just have to figure out how to get them (or get them past my filters, which are currently allowing only UPDATE_ROWS_EVENTv2 and WRITE_ROWS_EVENTv2)

# at 12893
#170221  4:33:21 server id 9975084  end_log_pos 12941 CRC32 0xf0b319b9
# Position  Timestamp   Type   Master ID        Size      Master Pos    Flags
#     325d 11 c3 ab 58   21   2c 35 98 00   30 00 00 00   8d 32 00 00   00 00
#     3270 01 37 a6 94 64 f5 8a 11  e6 93 fb 02 42 ac 14 00 |.7..d.......B...|
#     3280 03 11 00 00 00 00 00 00  00 b9 19 b3 f0          |.............|
#   GTID [commit=yes]
SET @@SESSION.GTID_NEXT= '37a69464-f58a-11e6-93fb-0242ac140003:17'/*!*/;
# at 12941

[glycerine]

Ah... It looks like the GTID_EVENT is a separate event that occurs before (or after?) the event that it labels.

[glycerine]

So the sequence of the binlog leading up to a RowsEvent for my data, seems to be:

GTIDEvent,  which says SET @@SESSION.GTID_NEXT= 'uuid:57'/*!*/;
QueryEvent
TableMapEvent
RowsEvent

It's all there. The gtid just comes before the rows-event as a distinct and separate event, 3 events prior to the rows that it applies to.

[siddontang]

👍