|
[x]
Posted via EE Mobile
|
|
| Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again. |
|
|
|
|
|
[x]
The Solution Rating System
|
|
| With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating. - The Grade of the Solution
- The Zone Rank of the Expert Providing the Solution
- The Number of Author and Expert Comments
- The Number of Experts Contributing
- The Feedback of the Community
Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site. If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support. Thank you! |
|
|
|
|
Asked by kev1970 in Oracle 11.x Database
Using Oracle 11g and TOAD 9.7.2.5, I'm executing:
select *
from TestTable
where TestDate is null
but it's not giving me any results even though TestDate field has thousands of null entries.
I discovered the problem when TOAD failed to run "Copy data to another schema" because of a null column violation.
This problem appeared following my adding a date column with a not null constraint which Oracle 11 allowed me to do even though there were thousands of null (TestDate) entries.
I have worked around the copy problem by disabling the not null constraint in the destination table but why is my statement not returning any rows in the source schema?
After the copy, I ran the same statement (see above) in the destination schema and it brought back the results correctly however, as expected, it is not allowing me to enable the not null constraint.
20091111-EE-VQP-92 - Hierarchy / EE_QW_3_20080625
