2009/9/2 Jeremy Evans <[email protected]>: > DB << "create table t (a text, b text)" << "insert into t values > ('a', 'b')" > > I think that makes the code harder to read. If you can come up with a > good use case for having << return self, I'll certainly consider > switching it.
The only possible use for this that I can think of is if statements where joined (when chained) for a single communication burst - ie: a multi statement execute. Then this kind of usage might have a use. Other than that it just makes the code messier for no gain other than making it messy. On a side note, another use I've experienced/seen: I remember years ago, one of the first ORMs I ever used (might even have been in Python actually before I saw the light ;)) automatically wrapped chained statements into a single transaction. I personally don't like this behaviour anymore and prefer explicitly defining my transactions where required, but thought I'd share anyway. Clive --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en -~----------~----~----~----~------~----~------~--~---
