Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
Some good options to consider: SQL create table as statements. This way you can define multiple tables all in one file, that can be copy/pasted easily. It also matches a very common thing: SQL e...
Answer
#2: Post edited
by
matthewsnyder
·
2023-06-25T01:04:13Z (11 months ago)
- Some good options to consider:
- * SQL `create table as` statements. This way you can define multiple tables all in one file, that can be copy/pasted easily. It also matches a very common thing: SQL exercises in things like Leetcode.
- * CSV. It's a bit ugly, but it's very easy to work with it, and many command line programs can take CSV right from standard input which in turn can come straight from the clipboard. So you don't even have to paste, just copy, and with a CLI it's very possible to post concise, readable and sophisticated solutions on a site like this. Even if you use a GUI, CSV pastes well into virtually every spreadsheet editor. And of course you can easily export anything to CSV.
* Markdown tables. If you can do CSV, you can use an online converter to turn it into Markdown easily. Markdown, unlike CSV, is much easier to read without formatting, and Calc etc. can take it from the clipboard if you use "fixed width". But it's also nice for people who are reading it by eye.
- Some good options to consider:
- * SQL `create table as` statements. This way you can define multiple tables all in one file, that can be copy/pasted easily. It also matches a very common thing: SQL exercises in things like Leetcode.
- * CSV. It's a bit ugly, but it's very easy to work with it, and many command line programs can take CSV right from standard input which in turn can come straight from the clipboard. So you don't even have to paste, just copy, and with a CLI it's very possible to post concise, readable and sophisticated solutions on a site like this. Even if you use a GUI, CSV pastes well into virtually every spreadsheet editor. And of course you can easily export anything to CSV.
- * [Markdown tables](https://software.codidact.com/posts/288660/288698#answer-288698). If you can do CSV, you can use an online converter to turn it into Markdown easily. Markdown, unlike CSV, is much easier to read without formatting, and Calc etc. can take it from the clipboard if you use "fixed width". But it's also nice for people who are reading it by eye.
#1: Initial revision
by
matthewsnyder
·
2023-06-22T23:59:37Z (11 months ago)
Some good options to consider: * SQL `create table as` statements. This way you can define multiple tables all in one file, that can be copy/pasted easily. It also matches a very common thing: SQL exercises in things like Leetcode. * CSV. It's a bit ugly, but it's very easy to work with it, and many command line programs can take CSV right from standard input which in turn can come straight from the clipboard. So you don't even have to paste, just copy, and with a CLI it's very possible to post concise, readable and sophisticated solutions on a site like this. Even if you use a GUI, CSV pastes well into virtually every spreadsheet editor. And of course you can easily export anything to CSV. * Markdown tables. If you can do CSV, you can use an online converter to turn it into Markdown easily. Markdown, unlike CSV, is much easier to read without formatting, and Calc etc. can take it from the clipboard if you use "fixed width". But it's also nice for people who are reading it by eye.