Postgresql 9.1 runs over the theme “features, innovation and extensibility” and it really does. This version was born to overcome Postgresql 9.0 ‘s limitations and known bugs in replication. If you are developing over 9.0, it’s time to think seriously about preparing your code for Postgresql 9.1.
It’s hard to believe the year is already coming to a close. As 2014 ends, it’s time to celebrate the holiday season with our WordPress.com tradition of teaming up with talented artists to create a cheerful WordPress illustration. This year, Mads Berg has dreamed up a scene of togetherness to capture the spirit of the season.
Percona Live: London was a rousing success for PalominoDB. I was sad that I could not attend, but I got a few people who sent “hellos” to me via my coworkers. But on to the most important stuff — slides from our presentations are online!
Today the sessions were more “high level” so don’t expect deep information and concrete implementations.
Roadmap to Cloud Infrastructure and Service Integration with cloud application foundation and SOA Suite
Frances Zhao-Perez and Simone Greib(Oracle)
Here Frances was talking about CAF (Cloud Application Foundation) which regroup products like weblogic, coherence and so on. She introduced the Oracle’s strategic investments list for this topic:
Jephe Wu - http://linuxtechres.blogspot.comEnvironment: SQL server 2008 Express edition on vcenter server, no SSMS installed by defaultObjective: learn how to truncate sql server database size in SQL Server Management Studio so that it won't exceed 10G limit, otherwise, database engine service will stop after 10G.
I think 2 years is long enough to wait between posts!
Today I delivered a session about Oracle Exadata Database Machine Best Practices and promised to post the slides for it (though no one asked about them :). I’ve also posted them to the Tech14 agenda as well.
Direct download: UKOUG Tech14 Exadata Security slides
The questions in the quiz were, of course, all trick questions.
Question 1: Answer D
SELECT * FROM T1 LEFT NATURAL JOIN T2;
SELECT * FROM T1 NATURAL LEFT JOIN T2;
The second example shows the correct syntax for a natural outer join. In the first example, LEFT is interpreted as a table alias for T1 and so an inner join is used.
QUESTION 2: Answer E
SELECT * FROM T1 INNER JOIN T2 ON C1=C2;
SELECT * FROM T1 OUTER JOIN T2 ON C1=C2;