I don't have that feature exactly, but I can offer this - if you have a table of regularly-formatted text data, you can paste it into the "Text-to-DDL" feature to have it automatically generate your CREATE TABLE and INSERT INTO statements.
Re: 2) Some day when I have a huge amount of free time, I would like to migrate to Groovy on Grails. Until then - CF is what I had used for over a decade, and it was the easiest thing for me to use to build with at the time (Jan 2012). I was more interested in getting something out there than using whatever the latest trendy tech.
Good point. I plan on building some help tips that explain how it works a bit better (beyond simply the examples which I have now) and that sounds like something worth including.
Also, a shout out to mrpollo (http://news.ycombinator.com/user?id=mrpollo) who helped me with the redesigned UI, after seeing the first post here on Hacker News. Thanks Ramon!
Thanks for the offer; at this point, testing and new ideas are the main things I'm looking for. Shoot anything my way : https://twitter.com/#!/sqlfiddle
I don't allow stored procedures or other programming (custom functions, triggers, etc...), because I worry about the danger of opening up that to the whole world. It should be pretty much open for any other standard database+sql commands you would need to do.
I've been meaning to add links to other useful SQL resources, such as that and http://dbdsgnr.appspot.com/. If you think of more ideas, I'd love to hear them - send me a message @sqlfiddle on twitter. Thanks!
Thanks for taking a look at it; sorry you found some bugs. I should point out that I only posted it publicly a week ago, and this has been my first traffic spike (thanks YCombinator!). I actually only started working on it less than three weeks ago, so I'm not surprised some boundary cases cause trouble. I've got more plans for it in the future. One thing I should note - a lot of people are working against the sample fiddles, but those are probably not where most people will be doing actual fiddling with their own queries, when they use the site for real. Different schema definitions are completely isolated (with little traffic), and so shouldn't see the sorts of problems you stumbled on.