Once upon a time I had a laugh on facebook when someone posted an image showing multiple groups dedicated to stopping duplicate groups, oh the irony.
Recently I've been trying to share my blog posts via LinkedIn but I'm always unsure which of the seven APEX groups I'm a member of I should post to.
Steven Feuerstein runs a great site at PL/SQL Challenge that is just another way for developers to stay up to date with their knowledge of PL/SQL, SQL and database design with a bit of fun.
PL/SQL championships are held quarterly, but the less frequent SQL and Database Design quizzes are currently held annually. Thanks to persistence and maybe a bit of experience, I was eligible to compete in both.
I've had this sitting my drafts for some time (it has company), thought it best I finally finish it off an move on.
Considering I fathered an awesome girl in January with my bare hands, surrounded by kangaroos with warm pouches waiting (some facts may have been distorted in this story), I think I did pretty well on the nerd front.
I get this email that tells me apexea.oracle.com is about to be fitted out with an even slicker APEX5 Early Adopter 3.
While playing with 12c I tried the upgrade to the DEFAULT column syntax that now allows sequences.
I came across a basic error, but it's just a small trap for new players.
CREATE TABLE seq_test(a NUMBER)
ALTER TABLE seq_test MODIFY (a NUMBER DEFAULT sage_seq.NEXTVAL)
SQL Error: ORA-02262: ORA-2289 occurs while type-checking column default value expression
*Cause: New column datatype causes type-checking error for existing column
default value expression.
If you're a semi-regular speaker looking for a new year's resolution, how about learning this little ditty?