readyset-sql: Change ordering of options in conversion

There is literally no good reason for this to be one order versus the
other, it just matches existing tests this way. If we cared about
preserving the input ordering, at some point we could upstream a fix to
sqlparser-rs which treats table options as a Vec (like column options)
instead of individual fields. But I think we only care about matching
the input for proxied queries where users may be trying to find a
specific query; DDL we don't generally show back to the user, and we
only care about some options and not their order.

Change-Id: Ic0130359d97255303d1d5d293806d2aec7a8b7c9

Author: mvzink

readyset-sql/src/ast/create.rs

@@ -179,14 +179,16 @@ impl TryFromDialect<sqlparser::ast::CreateTable> for CreateTableStatement {
         dialect: Dialect,
     ) -> Result<Self, AstConversionError> {
         // XXX: We don't actually care about most table options, and don't cover the DATA DIRECTORY
-        // variant because sqlparser doesn't support it.
+        // variant because sqlparser doesn't support it. Note that this is likely change the
+        // ordering of the options compared to the original SQL, since sqlparser stores them as
+        // individual fields instead of a list of options.
         let mut options = vec![];
-        if let Some(auto_increment) = value.auto_increment_offset {
-            options.push(CreateTableOption::AutoIncrement(auto_increment as u64));
-        }
         if let Some(engine) = value.engine {
             options.push(CreateTableOption::Engine(Some(engine.name)));
         }
+        if let Some(auto_increment) = value.auto_increment_offset {
+            options.push(CreateTableOption::AutoIncrement(auto_increment as u64));
+        }
         if let Some(charset) = value.default_charset {
             options.push(CreateTableOption::Charset(CharsetName::Unquoted(
                 charset.into(),