Its like due to the fact that in 5.6 the database was changed from a 3rd party tool to a proprietary one. My guess is that since its a brand new feature in a new release that this is an unexpected bug that didnt crop up in testing.
↧
Its like due to the fact that in 5.6 the database was changed from a 3rd party tool to a proprietary one. My guess is that since its a brand new feature in a new release that this is an unexpected bug that didnt crop up in testing.