In Percona’s white paper “Performance at Scale: Keeping Your Database on Its Toes,” we take a high-level approach to what you need to think about when planning for database scalability.
COURSE of the MONTH
10 days, 23 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
SQL Where statement - column_name(+)
Posted on 2013-01-07
I have inherited some old code and am wondering why the (+) was coded in this statement, as I have never seen it used before, and can find no reference to it on the internet.
WHERE c.CASE_NUMBER = cz.CASE_NUMBER(+)
Thanks
WHERE c.CASE_NUMBER = cz.CASE_NUMBER(+)
Thanks
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2-
2
5 Comments
Active 1 day ago
Hi tyler,
That's a legacy style of coding an outer join.
In the early days of SQL there were only inner joins. When outer joins were added, Oracle adopted the (+) syntax to describe that the table is being outer joined. (I've never cared for the syntax.)
As far as I know, it's not supported by any other vendor, and is deprecated by Oracle. The Oracle SQL parser still accepts the syntax, but you shouldn't use it to code new SQL projects.
Good Luck,
Kent
That's a legacy style of coding an outer join.
In the early days of SQL there were only inner joins. When outer joins were added, Oracle adopted the (+) syntax to describe that the table is being outer joined. (I've never cared for the syntax.)
As far as I know, it's not supported by any other vendor, and is deprecated by Oracle. The Oracle SQL parser still accepts the syntax, but you shouldn't use it to code new SQL projects.
Good Luck,
Kent
Active today
Here is the doc link that talks about it:
http://docs.oracle.com/cd/E11882_01/server.112/e26088/queries006.htm#SQLRF52354
I'm on fence with Kdo's post. I've been Oracle and only Oracle for so long, I've still not quite mastered the ANSI join syntax and find it confusing (but I also haven't taken the time to figure it out).
http://docs.oracle.com/cd/E11882_01/server.112/e26088/queries006.htm#SQLRF52354
I'm on fence with Kdo's post. I've been Oracle and only Oracle for so long, I've still not quite mastered the ANSI join syntax and find it confusing (but I also haven't taken the time to figure it out).
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
I'm trying, I really am. But I've seen so many wrong approaches involving date(time) boundaries I despair about my inability to explain it. I've seen quite a few recently that define a non-leap year as 364 days, or 366 days and the list goes on.
…
This post looks at MongoDB and MySQL, and covers high-level MongoDB strengths, weaknesses, features, and uses from the perspective of an SQL user.
- Query Syntax
- SQL
- Databases
- MySQL Server
- MongoDB
- NoSQL Databases, Percona
This video shows how to recover a database from a user managed backup
This video shows how to configure and send email from and Oracle database using both UTL_SMTP and UTL_MAIL, as well as comparing UTL_SMTP to a manual SMTP conversation with a mail server.
Suggested Courses
Course of the Month10 days, 23 hours left to enroll
770 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.