Skip to main content

Travel tip for Kscope15 and Beyond: Bring a water bottle!

I encourage everyone attending Kscope15 to take a vow:

I will not drink water from a disposable plastic bottle.

It won't be hard to find them. I imagine the conference organizers will provide them by the bushel.

But remember: every piece of plastic you consume will haunt the planet for hundreds, probably thousands of years.

The worst thing to use plastic for is something disposable.

And bottled water? Much of it is not even cleaner or "better" than tap water (though it will almost certainly have filtered out the nasty chlorine taste). Much of it is actually nothing more than filtered tap water (for example, Dasani-Coke).

Instead, bring a steel water bottle (best not to drink or eat out of plastic altogether - there are many inexpensive such bottles available via Amazon and so forth). Refill it as needed.

If lots of us foreswore plastic water bottles at Kscope15, we could reduce landfill and waste by hundreds of bottles. ODTUG would likely even save some money.

And if you forget or can't get hold of a reusable water bottle, no worries! Drink the water from your first and only disposable plastic bottle - and then reuse it for the rest of the conference!

On behalf of Planet Earth and all of its inhabitants, I thank you!

Comments

  1. Patrick BarelJune 18, 2015 at 8:42 AM

    How about the Dopper (http://dopper.com/) bottle. It is supposed to be made out of recycled plastic and you can even send your broken bottles so they can recycle those.

    ReplyDelete
  2. Steven FeuersteinJune 18, 2015 at 9:01 AM

    Thanks, Patrick. Sure, that's better than ahem virgin plastic. But the plastic is almost certainly leaching out chemicals into your water. It is far less inert and safe than stainless steel.

    ReplyDelete
  3. Patrick BarelJune 19, 2015 at 1:33 PM

    They also have a stainless steel version: https://dopper.com/shop/dopper-steel/

    ReplyDelete
  4. JonasJune 22, 2015 at 11:11 AM

    Hi Steven!
    Really, really cool that You care!!! Nice 2 see that Your try to change something!!! It is always a pleasure to read Your posts!

    I also found a cool bottle for myself: https://www.soulbottles.com/de/

    Keep on posting! You are great!

    ReplyDelete
  5. Steven FeuersteinJune 23, 2015 at 3:10 AM

    I am very pleased to say that ODTUG included a very nice glass water bottle in their conference bag. I should have expected no less. Great conference so far!

    Especially proud to have announced the Oracle Database Developer Choice Awards. Check them out: bit.ly/OracleDevChoice

    ReplyDelete

Post a Comment

Popular posts from this blog

Running out of PGA memory with MULTISET ops? Watch out for DISTINCT!

A PL/SQL team inside Oracle made excellent use of nested tables and MULTISET operators in SQL, blending data in tables with procedurally-generated datasets (nested tables).  All was going well when they hit the dreaded: ORA-04030: out of process memory when trying to allocate 2032 bytes  They asked for my help.  The error occurred on this SELECT: SELECT  *    FROM header_tab trx    WHERE (generated_ntab1 SUBMULTISET OF trx.column_ntab)       AND ((trx.column_ntab MULTISET             EXCEPT DISTINCT generated_ntab2) IS EMPTY) The problem is clearly related to the use of those nested tables. Now, there was clearly sufficient PGA for the nested tables themselves. So the problem was in executing the MULTISET-related functionality. We talked for a bit about dropping the use of nested tables and instead doing everything in SQL, to avoid the PGA error. That would, however require lots of wo...
4 comments
Read more

How to Pick the Limit for BULK COLLECT

This question rolled into my In Box today: In the case of using the LIMIT clause of BULK COLLECT, how do we decide what value to use for the limit? First I give the quick answer, then I provide support for that answer Quick Answer Start with 100. That's the default (and only) setting for cursor FOR loop optimizations. It offers a sweet spot of improved performance over row-by-row and not-too-much PGA memory consumption. Test to see if that's fast enough (likely will be for many cases). If not, try higher values until you reach the performance level you need - and you are not consuming too much PGA memory.  Don't hard-code the limit value: make it a parameter to your subprogram or a constant in a package specification. Don't put anything in the collection you don't need. [from Giulio Dottorini] Remember: each session that runs this code will use that amount of memory. Background When you use BULK COLLECT, you retrieve more than row with each fetch, ...
4 comments
Read more

PL/SQL 101: Three ways to get error message/stack in PL/SQL

The PL/SQL Challenge quiz for 10 September - 16 September 2016 explored the different ways you can obtain the error message / stack in PL/SQL. Note: an error stack is a sequence of multiple error messages that can occur when an exception is propagated and re-raised through several layers of nested blocks. The three ways are: SQLERRM - The original, traditional and (oddly enough) not currently recommended function to get the current error message. Not recommended because the next two options avoid a problem which you are unlikely  to run into: the error stack will be truncated at 512 bytes, and you might lose some error information. DBMS_UTILITY.FORMAT_ERROR_STACK - Returns the error message / stack, and will not truncate your string like SQLERRM will. UTL_CALL_STACK API - Added in Oracle Database 12c, the UTL_CALL_STACK package offers a comprehensive API into the execution call stack, the error stack and the error backtrace.  Note: check out this LiveSQL script if...
5 comments
Read more