Problems with Oracle SQL
241–250 of 277 posts
Re: Problems with Oracle SQL
#242[deleted]
Re: Problems with Oracle SQL
#243Re: Problems with Oracle SQL
#244From a security perspective, keep in mind the errors like "access denied" or "password invalid" are typically bad not good when compared to more generic "table does not exist" or "failed logon attempt". These errors tell you something positive about the existence of something you don't have the rights to know about and that is a defect in my opinion. I not saying good error messages are not valuable or that Oracle's…
> Table does not exist or you do not have access. Please contact your DBA if it should exist.
For login, assuming sql*plus
> Either you have an invalid password, user does not exist, or database cannot be found at this endpoint. Please contact your DBA if it should exist.
Re: Problems with Oracle SQL
#245I have worked with the Oracle database for six years and haven't had any major issues with error messages, in fact I'd say Oracle did a really great job building an amazing database.
Error returned: "ORA-00907: missing right parenthesis"
Am I using Oracle wrong? No. It's a tool and CTEs are supported. Ergo the error message is an issue since it is not descriptive of the actual issue.
Re: Problems with Oracle SQL
#246So many comments here about MS and Oracle. Mēh! I have an intellectual affinity for the suffering. But it has been 20 years since I wrestled with the Beast from Seattle. Most of those twenty years were spent doing my own things in Linux, Perl, and R. In glorious ivory tower isolation from the real world consequences of serving a master who's goal was to extract revenue... Here I am for the last year serving Apple (th…
Re: Problems with Oracle SQL
#247Earlier quoted context omitted.
Such as?
All the apps they bought. Siebel, PeopleSoft, BEA Weblogic. I was the DBA for a Siebel instance for ten years. I would say J.D. Edwards, but that's AS400/DB2. SAP is also a big driver, although they don't want to be (so much so that they bought Sybase).
Re: Problems with Oracle SQL
#248I've worked with databases for a while now and I've never advocated for moving to Oracle (I have advocated for postgres though). The long term organizational costs is a big factor - but an almost equally large factor is the fact that 1. I have never actually used their dialect and have heard absolutely terrible things about it 2. There is no non-enterprise DBMS available that uses something close to their dialect so…
The problem is the Oracle dialect was created BEFORE the SQL standard was written. For backwards compatibility they never changed it after the SQL standard was written. Personally, I think they should have had a flag so you could choose whether to use standard SQL or Oracle SQL.
Not that most Oracle DB ppl use it anyway.
Re: Problems with Oracle SQL
#249Earlier quoted context omitted.
> Sometimes I write the same script as PS and as bash script. That's your mistake! Don't write bash scripts in PowerShell, and don't write PowerShell scripts in bash. Don't be surprised if the shopkeeper can't understand you, when you're speaking "French" by translating an English sentence word for word. PowerShell is much more readable, terse, and elegant than Bash. It absolutely blows it out of the water... on Wind…
PowerShell elegant? Wow. No way. I've written hundreds of thousands of lines of PowerShell on Windows over the years. PowerShell is great for one-liners and very short scripts. It also has many cool hooks into the OS that makes things more comfy. That said, as soon as you need to write a modestly long script or need something remotely performant, you're going to want to reach for the nearest pencil to shove into your…
This is most obviously noticeable (to me at least), when debating ergonomics with people that prefer UNIX platforms, especially bash and text-based configurations. There was a study that showed that an action like moving a mouse to select a file feels slow because there's one slow movement, but selecting the file through typing at a console is perceived to be faster because there are many keystrokes in quick succession. People report that they prefer the latter for "the speed" even if it's an order of magnitude slower than the mouse if measured with a stopwatch.
The terse two-character commands of the UNIX world were an optimisation for teletype. As in a literal typewriter banging away on paper, at a rate of something like 10-30 cps. Modern (four-decade-old!) computers have tab complete, which makes this largely irrelevant.
Verbose commands are an enabler. They enable novice users to read scripts, instead of only masters being able to write them. Long, systematically and consistently named commands enable discovery through wildcard searches.
You cannot now -- nor ever will be able to -- do something like this in the Bash world:
Get-Command Get-Az*Disk*
That's not an option because Bash doesn't actually follow the UNIX philosophy: it's not composable, it's not orthogonal, it's not designed, it's not self-consistent, etc...It's a clever hack around byte streams that people have slowly built up over decades, evolving over time haphazardly. There was an 'sh' for example!
PS: You talk about using Python instead of scripting languages, which is actually a fine choice that I won't argue with. But have you considered writing "heavyweight" PowerShell modules in C#? As in, a proper DLL module? It's mindblowing how productive it is compared to trying to write a command line tool in C/C++, or any other language for that matter. Automatic input validation, input parameter name tab-complete, pipeline handling, all wired up with a handful of attributes...
Re: Problems with Oracle SQL
#250It seems to be the general rule of thumb that, when you want to google for an oracle error message, then exclusion of both oracle documentation site, and developer forums is your first criteria on the search bar. Same applies to Microsoft (large parts of MSDN), and now Amazon Web Services documentation (at least some parts of it). That's the reason StackOverflow works - it really solves programmer's problems, instead…
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.