16,008,010 members
Sign in
Sign in
Email
Password
Forgot your password?
Sign in with
home
articles
Browse Topics
>
Latest Articles
Top Articles
Posting/Update Guidelines
Article Help Forum
Submit an article or tip
Import GitHub Project
Import your Blog
quick answers
Q&A
Ask a Question
View Unanswered Questions
View All Questions
View C# questions
View C++ questions
View Javascript questions
View Visual Basic questions
View .NET questions
discussions
forums
CodeProject.AI Server
All Message Boards...
Application Lifecycle
>
Running a Business
Sales / Marketing
Collaboration / Beta Testing
Work Issues
Design and Architecture
Artificial Intelligence
ASP.NET
JavaScript
Internet of Things
C / C++ / MFC
>
ATL / WTL / STL
Managed C++/CLI
C#
Free Tools
Objective-C and Swift
Database
Hardware & Devices
>
System Admin
Hosting and Servers
Java
Linux Programming
Python
.NET (Core and Framework)
Android
iOS
Mobile
WPF
Visual Basic
Web Development
Site Bugs / Suggestions
Spam and Abuse Watch
features
features
Competitions
News
The Insider Newsletter
The Daily Build Newsletter
Newsletter archive
Surveys
CodeProject Stuff
community
lounge
Who's Who
Most Valuable Professionals
The Lounge
The CodeProject Blog
Where I Am: Member Photos
The Insider News
The Weird & The Wonderful
help
?
What is 'CodeProject'?
General FAQ
Ask a Question
Bugs and Suggestions
Article Help Forum
About Us
Search within:
Articles
Quick Answers
Messages
Comments by Member 10104822 (Top 8 by date)
Member 10104822
28-Feb-18 8:09am
View
You are a genius sir.
Thank you very much!
Member 10104822
28-Feb-18 7:26am
View
That's the thing. I need to be able to insert one row at a time into the target table and query that table before each new row is inserted.
That is the crux of the problem really
Member 10104822
28-Feb-18 7:00am
View
unfortunately this does not work. I get the error;
Invalid operation: operator does not exist: character varying =@ character varying;
Are you using variables? Redshift does not support variables unfortunately
Member 10104822
28-Feb-18 6:24am
View
It is.empty
Member 10104822
28-Feb-18 6:09am
View
It is
Member 10104822
28-Feb-18 5:53am
View
This scenario can't occur. There will always be on overlap.
it would go from
A1 -> A2 -> B2 or vice versa.
You'll always have an overlap.
Member 10104822
28-Feb-18 4:46am
View
Correct
Member 10104822
27-Feb-18 14:40pm
View
This is not a contrived exercise. The data supplied is just analogous dummy data. All I'm saying is that for what i need this for, if there are conflicts then i dont need to add some additional logic to determine the correct value. It can be ordered first but for simplicities sake its not needed
Show More