Opened 3 years ago

Last modified 3 years ago

#24562 new enhancement

Define SQL coding guidelines for Metrics' products

Reported by: iwakeh Owned by: metrics-team
Priority: Medium Milestone:
Component: Metrics Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Some points with examples are stated in #24218 comment 8. We shouldn't re-invent the wheel here. Thus, for reference some ideas from Oracle and another reference suggested there.

I wouldn't want to copy these entirely, especially the 'space before comma' rule is troublesome. We don't change sql often enough to justify that.

There are probably other nice references out there, which should be considered.

Child Tickets

Change History (2)

comment:1 Changed 3 years ago by iwakeh

Summary: Define SQL coding guidelines for Merrics' productsDefine SQL coding guidelines for Metrics' products

Corrected typo (maybe, I wrote Merrics earlier b/c of the season ;-)

comment:2 Changed 3 years ago by irl

If there is to be a reimplementation of Onionoo using a relational database backend, this would be particularly useful for that.

Note: See TracTickets for help on using tickets.