No ORM's

[Melkeydev]

As go-blueprint adds more features and expands into DB layers, I am going to make the decision to not include an ORM. The reason being:

• ORM's can be opionated
• Majority should know SQL > a particular ORM
• Not to bloat the CLI with too many options that can cause a worse user experience

[pka420]

Please Let us add something like folder structure to handle: apis/ models/ db/ etc...

and NO ORM.

[StevenACoffman]

It is not an ORM, so What do you think of sqlc, which is not an ORM, but a SQL-to-Go compiler that generates Go models and functions based on your SQL schema and queries?