The primary key columns don't have to be in the same order as the table columns
Add unittest for primary key columns don't have to be in the same order as the table columns
Code the primary key ordering so it works with sqlite before version 3.7.16
Skip test on sqlite versions where this can't work
Make the column more predictable

Take the column order into account and sort non PK columns last
"0" columns location doesn't matter
Allow mysql spatial indexes
Add reverse engineering part for spatial indexes
Document known issue about reverse engineering primary key order in sqlite
ORACLE, (INSTANCE_NAME = XXXXX)

Hello, first sorry for my English. 
I need to put in the ORACLE Connection string to the parameter: (INSTANCE_NAME = XXXXX) 

I was reading the source code at github and the latest version does not include this possibility in the method getEasyConnectString. 

Could add to the next version an element in the array of parameters, eg $params['instance_name'] and concatenating that value to the Connection string? 

Thank you, greetings 
Facundo Panizza
Change parameter instance_name by instancename

Change the name of the parameter instance_name by instancename
Add the instancename parameter for oci8 driver

We add the instancename parameter documentation for oci8 driver
Update configuration.rst
Merge pull request #544 from facupanizza/master

ORACLE, (INSTANCE_NAME = XXXXX)
Merge pull request #541 from jsor/mysql-spatial-index

Allow mysql spatial indexes
Merge pull request #516 from bartv2/sort-sqlite-pk-columns

The primary key columns don't have to be in the same order as the table columns
fix reverse engineering LOB type column types in MySQL
fix integer 0 default value reverse engineering on SQL Anywhere
fix LOCATE expression on SQL Anywhere
fix LOCATE expression offset evaluation on SQLite