181–190 of 277 posts
So I've used MySQL at a very basic level but for the last couple of years almost solely been on Oracle because that's what my org uses. I sporadically dabble in the db stuff but am mostly working on front end. What's the db most people use now, Postgres? Could someone point me towards a good resource for it?
Earlier quoted context omitted.
So how do you insert an empty string into a NOT NULL column? Please don't tell me that it's not possible.
Honestly that's bad db design anyways. If empty string is a valid value then you don't want NOT NULL anyways. This is a table structure constraint, not a variable declaration. NOT EMPTY would have been a better syntax imo but that's a whole can of worms.
Earlier quoted context omitted.
So spoiled by Rust now when using one of these "documented" APIs. * Rust's examples work, because the default behaviour of Rust's automated testing is to test your documented examples (as well as any unit tests you wrote), so, it's actually more effort to write examples that don't work. If you're too lazy for that, you're going to not write any examples, so then I at least know I'm in uncharted territory. * The relev…
A thing that helps with Rust, in my opinion, is that the language is statically typed and people mostly write functions. That makes it easy to glue the pieces together in my head. So even if the documentation isn't great, I can find a way to do what I want.
The thing that kills me about Oracle is that since the license does not allow benchmarking, we (or at least I) don't know how it actually stacks up to the competition. Of course, that's the idea, but it would be cool to have that data.
What?! How do they disallow people from benchmarking it? Do they just forbid people from benchmarking in legal terms? That sounds so fishy.
There was a comment on here a few years ago from a developer with experience working on the Oracle database codebase which put me off it for life: https://news.ycombinator.com/item?id=18442941
thats quite beautiful in its scale of monstrousness
Earlier quoted context omitted.
I don’t work with Microsoft stuff as much anymore, but my big beefs with Microsoft product documentation are: - It is was often unclear what version of the “thing” was in scope. An article from product version X will reference X-1 documention. - Microsoft will gaslight you. If you interact with them on a significant issue, you need to snapshot their product docs. I’ve worked with Premier on issues when pushing produc…
Microsoft is a complex and big entity. While most of it is doing a bad job whatever it is, some parts are quite good. In particular now that the C# stack is fully open, it's very easy to report a bug (on GitHub) and developers are reactive from my experience (submitted a bug impacting the dotnet SDK).
Earlier quoted context omitted.
I feel Postgres and SQL Server are easier to grok error states. Oracle seems to want to be an application platform more than a datastore
I don't have the experience to compare them to Oracle, but SQL Server and Postgres do have their own issues. The infamous MSSQL "string or binary data will be truncated" error (fixed a while ago[0]), or the way either deals with unqualified access to columns which leads to surprises (e.g. in MSSQL subqueries or in Postgres's SECURITY DEFINER procedures). [0] https://docs.microsoft.com/en-us/sql/t-sql/database-console…
Oracle seems to have more than most, IMO.
I have a journeyman data engineering level experience with each. Rare combo I guess, Data Scientist focus.
Earlier quoted context omitted.
I'm not sure why the hate against MSDN - at least for .NET, I found the documentation to be one of the best in the business -even a decade ago. I'd only put Go's docs ahead in terms of helpfulness. I cut my teeth writing .NET code, then switched to Java writing apps on Android - the step down in doc quality was quite significant.
MSDN isn't terrible, but for answers.microsoft.com 90% of questions are some outsourced foreign support rep telling the user to run sfc /scannow and not looking into the issue any further. Which makes it a huge pain for sysadmin type stuff, their developer documentation is much better.
Earlier quoted context omitted.
> Oracle it not that bad anyway, it's just stupidly expensive. Full of bugs, some that destroy speed, some that destroy data, some that just make a feature that you need unusable. More heavyweight than lead (although it gets fast after you throw enough hardware). Lacking any capable or usable management interface (but then, that excludes everyone except for postgres and mysql). Impossible to program. Impossible to pr…
> comes with the Oracle legal team This would've been sufficient, honestly.
Did I say it has bugs?