It amazes me SAP makes so much money...
-
Jeremy Falcon wrote:
using text fields for boolean logic
To be fair, a boolean isn't part of the ISO specification (Oracle, for example, doesn't have a boolean data type). So you either use a numeric type and restrict it to 0 and 1 or you use a text type and restrict it to Y and N. I've seen the Y/N a lot (although I don't agree with it). At least be glad they documented it properly! What's more important, the average user will never see any of this. What matters to them is that it works and gives them the functionality they need and somehow it does. They don't care about your petty programmer problems like casting Y/N to booleans and keeping your data consistent without foreign keys.
Best, Sander arrgh.js - Bringing LINQ to JavaScript SQL Server for C# Developers Succinctly Object-Oriented Programming in C# Succinctly
Actually, a byte for a character and a bit are frequently implemented the same: takes one bit of the eight for the value and ignores the other seven. An int would be four bytes; short int could be as small as two. So just about anyway you cut it, Y/N isn't that bad of choice. It is even self documenting!
-
Surely, I can't be the only person to go through bits of SAP and think, if they can sell this, then in tech you apparently can pretty much shrink wrap and sell a turd to people who don't know any better. The more I dig into SAP the more WTFs I see. For instance... SAP Business One 8.8 Administration system ADP1 table definitions[^] From this one table alone I can see 3 problems at least... archaic naming convention, using text fields for boolean logic, and not using an ENUM field or lookup table where appropriate. More if I try, and this isn't counting the fact there are no foreign keys in the database, some of the denormalized data I've seen, and some stored procs with unnecessarily needed hard coded values. :doh:
Jeremy Falcon
It also amazes me that Citrix got installed in so many places - must be the CEO who bought it on the basis of "zero admin costs" and "reducing PC estate" claims.... Every infrastructure team I've ever spoke to about it HATE it and spend more time supporting it than they ever did with proper PC desktops....
-
Surely, I can't be the only person to go through bits of SAP and think, if they can sell this, then in tech you apparently can pretty much shrink wrap and sell a turd to people who don't know any better. The more I dig into SAP the more WTFs I see. For instance... SAP Business One 8.8 Administration system ADP1 table definitions[^] From this one table alone I can see 3 problems at least... archaic naming convention, using text fields for boolean logic, and not using an ENUM field or lookup table where appropriate. More if I try, and this isn't counting the fact there are no foreign keys in the database, some of the denormalized data I've seen, and some stored procs with unnecessarily needed hard coded values. :doh:
Jeremy Falcon
Having worked with SBO for many years I can tell you that there are plenty more surprises in store for you... Just wait til you dig deeper and have the pure joy of things like OITM.VatGourpSA (wtf?) or OCPR.E_mailL. Many field names seem like they ran out of vowels (CIN13.LstPchPrce). The thing that drive me nuts in the early days was the 4 character table names. Because, clearly RDR12 is Order Address Extension Data......anyway let me know if you get stuck with anything :)
-
Having worked with SBO for many years I can tell you that there are plenty more surprises in store for you... Just wait til you dig deeper and have the pure joy of things like OITM.VatGourpSA (wtf?) or OCPR.E_mailL. Many field names seem like they ran out of vowels (CIN13.LstPchPrce). The thing that drive me nuts in the early days was the 4 character table names. Because, clearly RDR12 is Order Address Extension Data......anyway let me know if you get stuck with anything :)
Man, it's like you know my pains. I may take you up on that offer if you don't mind. Although, we're using a plug-in that adds vendor specific tables into the DB, I'm sure you're knowledge would be invaluable.
Jeremy Falcon
-
Jeremy Falcon wrote:
people in this industry trying to "show off knowledge"
I'll show off with my books and articles, no lounge post can tip that :) I really only mentioned that just to show off.
Jeremy Falcon wrote:
Maybe, but I'd rather be an ass than a SAP developer. :)
What's the difference? :laugh:
Best, Sander arrgh.js - Bringing LINQ to JavaScript SQL Server for C# Developers Succinctly Object-Oriented Programming in C# Succinctly
Sander Rossel wrote:
I really only mentioned that just to show off.
:laugh: Touché!
Jeremy Falcon
-
Man, it's like you know my pains. I may take you up on that offer if you don't mind. Although, we're using a plug-in that adds vendor specific tables into the DB, I'm sure you're knowledge would be invaluable.
Jeremy Falcon
no worries - drop me a line here or email me anytime.
