Best practice to store long SQL files with you project

[Zvoni]

I was just thinking about OP's original request to manage the multiline sql into source code.

I normally keep sql in code, even if I understand that somebody prefers to store in external files, because in turn, sql in code means loaded in memory while program runs and this is kinda senseless.

With the downside, that if you HAVE to change your SQL-Statement (for whatever reason), you have to recompile/redistribute

I like using json for that or xml, having query name as key and sql text as content. That said I definitely do not split sql into separate lines, but this is just my personal way of seeing the world. All in one line (sometimes is very long!).

Yep, for me too: Once a Statement is written, it ends up in one single line, because that's what it is in the end

[Чебурашка]

If you HAVE to change your SQL-Statement (for whatever reason), you have to recompile/redistribute

True 100%, although seldomly sql changes and code not.

[Okoba]

@Hansvb I am sure you and many other needed to have SQL queries and especially big ones in your code. And having an ugly SQL-To-Pascal output like my first post, is not very cool.

[incendio]

For me, use a stored procedure for long sql queries.