Seriously, the person who thought creating a monster like OpenSQL should be shamed in public. This thing really is the pinnacle of misanthropy and working with it feels like having a constant root canal treatment.

well, it's SAP, so you know it's garbage.

it's not designed to be usable. it's designed to generate high support revenue.

(also: oh, the irony of defining a proprietary standard and calling it "openSQL")

Very much enterprise Software. They want to survive no matter the cost.

@tosensei This is what struck me as well. Why call it "open" when it's the most closed shit you could ever imagine?

@CodingTripledad 'cause they'll use it to open your purse, i guess.

How is it different from regular issue sql?

Does it really have Wikipedia pages only in German and Spanish?

@Lensflare It starts with funny parts like having to use ~ instead of . for column selection, then you have spaces that matter, as in max(n) gives you an error, cause the syntax is max( n ). It goes on with subselects not working, CTEs should work, but not for me. Then you have certain cases where you can nest functions, sometimes not, so for instance select 'bla' && 'bla' && 'bla' works, select concat( 'bla', concat( 'bla', 'bla' ) ) does as well, but not select case when 1 then 'bla' else 'blo' && 'bla' ... in that case you'd have to work with concat again. it drives you mad cause everything almost any modern DB can do, this shit can't. Reason? OpenSQL is made to act as a layer that can use the query on any kind of database.

@CodingTripledad holy crap, what a piece of shit!

@electrineer I'm not sure. I'm German so I didn't care too much, but knowing German definitely helps when reading the tables, cause the table and column names have strange names derived from their German full names, so like the table VBAK will contain header data (K = Kopf) and VBAP will hold item data (P = Position). They have views to make life a bit easier, but it's still far from intuitive.