modules.api.sql.select and the order of fields

[senikk]

I'm concerned about the need for the fields to be ordered just like they exists in the blockchain.db and if you join with system table like often used in the examples like "transactions" if Lisk team decide to add a new field in "transactions" every dapps which updates the SDK breaks.

[TheGoldenEye]

Using the "fields" option you can specify the columns and their order you need.
Example:

modules.api.sql.select(
  {
  table: "transactions",
  alias: "t",
  fields: [{"t.senderId": "senderId", "t.senderPublicKey": "senderPublicKey", "t.recipientId": "recipientId", "t.id":"transactionId"}],
  condition: 
    {
    recipientId: query.recipientId,
    type: self.type
    },
  join: [
    {
    type: 'left outer',
    table: 'asset_messages',
    alias: "tm",
    on: {"t.id": "tm.transactionId"}
    }]
  }, ['senderId', 'senderPublicKey', 'recipientId', 'transactionId'], 
  function (err, transactions) { ...}