On Apr 19, 4:20 pm, Jeremy Evans <[email protected]> wrote: > > You'll have to be a bit more specific about what you want in this > case. I think you might be referring to something like the SteamCode > blog entries on Sequel and Ramaze, but I'm not sure. I'm OK with the > idea of tutorials in general, but there would need to be a pretty > strong focus on teaching Sequel usage as opposed to just solving a > usually contrived problem. I guess this is an area where I'd probably > judge each proposed addition on it's own merits. >
Might I suggest for consideration a CONTEST? People submit the description of a real world SQL problem that they have had and the SQL code they used to solve it. When the period for problem submissions ends, say 10-14 days, the list members vote for the top 3 (or more if desired) problems based on the technical issues raised. Once the N winning problems are selected then people can submit their best efforts at solving one or each of the problems using Sequel. They must also provide a written explanation (can be inline comments) of what they did and why they did it that way. After another two weeks or so we vote on the merits of each of the solutions submitted. The winning pairs of problem and solution become your examples and both the problem submitter and the Sequel solver get their names associated with the examples. The problems submitted MUST have been solved by the submitter using SQL and the SQl solution provided. I think that this would greatly reduce the likelihood of the problems being contrived. Further, there is no need for the problem submitter to necessarily have a Sequel solution to offer. Likewise there is no need for the Sequel solution to come from anyone that submitted a problem. WDYT? -- 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.
