I only just started to look into Sequel, to see if it is a better fit for us than ActiveRecord. My first impression is good, but I am running into an issue. We use MS SQL via TinyTds. All of our tables have a TimeStamp column, that is of the type timestamp, or ROWVERSION in recent versions of SQL server. NB: this is NOT a datetime field. It contains 8 bytes; with every update of a record, the value of this field increases. This helps to implement optimistic concurrency.
A timestamp field should be treated as read-only, but the piece of code of Sequel that creates UPDATE statements, tries to update this field. Of course, this fails miserably. The best solution would be for Sequel to exclude this type of fields from UPDATE and INSERT statements. A workaround could be to specify the columns in the .save instruction, excluding the timestamp field. Not very nice. Any suggestions for a quick solution? -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/groups/opt_out.
