what are we ? we are what we experience. And some more. I bring together here, collective experiences from different parts of life..
Sunday, May 30, 2010
An interesting essat on flyovers [in Indian context]
निम्नलिखित लेख उस छात्र की कॉपी से लिया गया है, जिसे निबंध लेखन
प्रतियोगिता में पहला पुरस्कार मिला है। निबध का विषय था - फ्लाईओवर।
फ्लाईओवर का जीवन में बहुत महत्व है, खास तौर पर इंजीनियरों और ठेकेदारों
के जीवन में तो घणा ही महत्व है। एक फ्लाईओवर से न जाने कितनी कोठियां
निकल आती हैं। पश्चिम जगत के इंजीनियर भले ही इसे न समझें कि भारत में यह
कमाल होता है कि पुल से कोठियां निकल आती हैं और फ्लाईओवर से फार्महाउस।
खैर, फ्लाईओवर से हमें जीवन के कई पाठ मिलते हैं, जैसे बंदा कई बार
घुमावदार फ्लाईओवर पर चले, तो पता चलता है कि जहां से शुरुआत की थी, वहीं
पर पहुंच गए हैं। उदाहरण के लिए ऑल इंडिया इंस्टिट्यूट ऑफ मेडिकल साइंसेज
के पास के फ्लाईओवर में बंदा कई बार जहां से शुरू करे, वहीं पहुंच जाता
है। वैसे, यह लाइफ का सत्य है, कई बार बरसों चलते -चलते यह पता चलता है
कि कहीं पहुंचे ही नहीं।
फ्लाईओवर जब नए-नए बनते हैं, तो एकाध महीने ट्रैफिक स्मूद रहता है, फिर
वही हाल हो लेता है। जैसे आश्रम में अब फ्लाईओवर पर जाम लगता है, यानी अब
फ्लाईओवर पर फ्लाईओवर की जरूरत है। फिर उस फ्लाईओवर के फ्लाईओवर के
फ्लाईओवर पर भी फ्लाईओवर चाहिए होगा। हो सकता है कि कुछ समय बाद फ्लाईओवर
अथॉरिटी ऑफ इंडिया ही बन जाए। इसमें कुछ और अफसरों की पोस्टिंग का जुगाड़
हो जाएगा। तब हम कह सकेंगे कि फ्लाईओवरों का अफसरों के जीवन में भी घणा
महत्व है।
दिल्ली में इन दिनों फ्लाईओवरों की धूम है। इधर से फ्लाईओवर, उधर से
फ्लाईओवर। फ्लाईओवर बनने के चक्कर में विकट जाम हो रहे हैं। दिल्ली
गाजियाबाद अप्सरा बॉर्डर के जाम में फंसकर धैर्य और संयम जैसे गुणों का
विकास हो जाता है, ऑटोमैटिक। व्यग्र और उग्र लोगों का एक ट्रीटमेंट यह है
कि उन्हें अप्सरा बॉर्डर के जाम में छोड़ दिया जाए।
फ्लाईओवर बनने से पहले जाम फ्लाईओवर के नीचे लगते हैं, फिर फ्लाईओवर बनने
के बाद जाम ऊपर लगने शुरू हो जाते हैं। इससे हमें भौतिकी के उस नियम का
पता चलता है कि कहीं कुछ नहीं बदलता, फ्लाईओवर का उद्देश्य इतना भर रहता
है कि वह जाम को नीचे से ऊपर की ओर ले आता है, ताकि नीचे वाले जाम के लिए
रास्ता प्रशस्त किया जा सके।
फ्लाईओवरों का भविष्य उज्जवल है। कुछ समय बाद यह सीन होगा कि जैसे डबल
डेकर बस होती है, वैसे डबल डेकर फ्लाईओवर भी होंगे। डबल ही क्यों,
ट्रिपल, फाइव डेकर फ्लाईओवर भी हो सकते हैं। दिल्ली वाले तब अपना एड्रेस
यूं बताएंगे - आश्रम के पांचवें लेवल के फ्लाईओवर के ठीक सामने जो फ्लैट
पड़ता है, वो मेरा है। कभी जाम में फंस जाएं, तो कॉल कर देना, डोरी में
टांग कर चाय लटका दूंगा। संवाद कुछ इस तरह के होंगे - अबे कहां रहता है
आजकल रोज अपने फ्लैट से पांचवें लेवल का जाम देखता हूं, तेरी कार नहीं
दिखती। सामने वाला बताएगा - आजकल मैं चौथे लेवल के फ्लाईओवर में फंसता
हूं। अबे पांचवें लेवल के जाम में फंसा कर, वहां हवा अच्छी लगती है। अबे,
ले मैं तेरे ऊपर ही था, पांचवें वाले लेवल पर और तू चौथे लेवल पर, कॉल कर
देता, तो झांककर बात कर लेता। आने वाले टाइम में दिल्ली वाले अपने
मेहमानों को फाइव डेकर जाम दिखाने लाएंगे।
Thursday, May 13, 2010
Parallel Querying using Oracle
Perhaps a long awaited feature, this one is clearly the one that I like most.
Using pre-built packages its now possible to break a single (relatively heavy) operation into multiple small operations, which run in parallel. The benefits are obvious, and cant be ignored.
I am yet to ascertain the usability of such a feature with tools like informatica or pentaho, but I am quite sure a lot can be achieved, especially in the direction of updates to huge tables in data warehouses.
And looking at the implementation, its genuinely simple and straightforward.
Would be nice to see more applications utilizing the benefits of such features..
Read more on Oracle magazine, article written by Steven Feuerstein...
Friday, May 7, 2010
101 Romantic ideas
2. Walk hand in hand in the rain.
3. Write a love poem.
4. Call a radio station and dedicate a favorite song.
5. Write "I Love You" in lipstick or shaving cream on the mirror.
6. Hide love notes in a lunch box, briefcase or purse.
7. Make heart-shaped cinnamon toast for breakfast.
8. Place a love note in the personals section of the newspaper.
9. Take a carriage ride around the city.
10. Plan a surprise getaway.
11. Do your mate's household chores.
12. Write notes on future dates in their date book ("I love you," I miss you," etc.)
13. Make reservations at a favorite restaurant.
14. Let them choose the movie.
15. Give a foot massage.
16. Make a heart-shaped bookmark, and place it in their book.
17. Pop in a romantic music CD and slow dance.
18. Throw a just-because surprise party for two.
19. Buy a stuffed animal for your honey.
20. Read each other's horoscopes.
21. Make a list of the top 10 things you love about your partner.
22. Display it in a prominent place.
23. Tattoo your mate's name on your body.
24. Make an album or scrapbook of your favorite memories together.
25. Go camping together and only take one sleeping bag.
26. Send a mushy message in a bottle...a balloon...a sandwich...
27. Cut out a silly cartoon that you know they'd enjoy.
28. Shower together.
29. Dim the lights, and snuggle together on the couch.
30. Be the first to say "I'm sorry" and kiss and make up.
31. Give each other a full-body massage.
32. Kiss every hour on the hour all day long.
33. Send a gift basket of indulgent items.
34. Write "I'm hot for you" in the steam on the bathroom mirror.
35. Ribbon wrap your bed with a big bow.
36. Fill up the gas tank of your partner's car.
37. Act like teenagers. Maybe even pierce something!
38. Show up with a bouquet of flowers -- for no reason at all.
39. Play Scrabble���� together, using as many "love" words as
you can.
40. Run a warm bubble bath for your partner, with lots of lit
candles.
41. Meet in the park for a picnic.
42. Hold hands.
43. Leave a trail of rose petals through the house, leading to a romantic candlelight dinner.
44. Make a donation in your mate's name to a special cause or charity.
45. Pick up their clothes from the floor -- without saying a word about it.
46. Watch an old black and white romantic movie and share a bowl of popcorn.
47. Reenact your first date.
48. Surprise your partner with tickets to a special event.
49. An unexpected hug can brighten any day.
50. Buy a silly, impromptu gift.
51. Send an email just to say "I'm thinking of you."
52. Bring home a balloon bouquet.
53. Serve breakfast in bed.
54. Make an ornament with a picture of both of you for the Christmas tree.
55. Play tag.
56. Wash and wax your partner's car, and leave a little note on the dashboard.
57. Plant a garden together.
58. Leave a mushy message on voicemail.
59. Stay at a hotel for the night, just because.
60. Make angels in the snow.
61. Every time you say "hello" or "goodbye", seal it with a hug and a kiss.
62. Take a drive in the country.
63. Spend the evening looking at the stars -- and make a wish together.
64. Cast a playful wink any time, anywhere.
65. Think up a list of silly little pet names for times when you're alone together.
66. Read poetry to each other.
67. Celebrate your half-birthdays together.
68. Put a picture of both of you in your wallet.
69. Buy that favorite book or CD for no reason at all.
70. Send a care package to work filled with treats like food, photos, candy, a love note, heart-shaped confetti, etc.
71. Go out for the evening and tell people you're on your honeymoon.
72. Take a hike together and carve your initials in a tree.
73. Write a thank you note for all the things you take for granted.
74. Make a fire in the fireplace and roast marshmallows.
75. Tape your favorite TV show and spend the evening talking.
76. Do the dishes together, then apply hand lotion to each other's hands.
77. Write a love letter to your partner and cut it into jigsaw puzzle pieces.
78. Decide on secret signals and use them to communicate with each other in large groups of people.
79. Schedule a regular mid-week "date night" for just the two of you.
80. Do the laundry together.
81. Romance Theater Weekend: reenact each other's favorite love scene - hers on Friday, his on Saturday.
82. Call your partner at work and ask for a date.
83. Pretend you haven't seen each other for a month. Actaccordingly.
84. Send a written invitation to do something special.
85. Take turns reading to each other.
86. Stand outside the window and sing a romantic song.
87. Hide favorite candy in your partner's coat pockets.
88. Put a tape recording of your voice (saying anything) in the
car stereo and turn it on so it plays when the car starts.
89. Go to a drive-in movie.
90. Get up to turn off the last light after you're both
comfy-cozy in bed.
91. Hold each other tight during a thunderstorm.
92. Make a tape recording of favorite love songs.
93. Leave a bunch of bananas on the kitchen table with a note, "I
go bananas over you!"
94. Hide love notes in a magazine.
95. Declare your undying love via a telegram.
96. Make a romantic dinner together, and serve it on your finest
china.
97. Surprise your partner with a big kiss on the neck.
98. Give unexpected compliments.
99. Share an ice cream cone.
100. Have a picnic on the living room floor.
101. Draw a silly picture of the two of you. Frame it.
Thursday, May 6, 2010
Working of oil wells..
I personally like such diagrams and explanations. not that an accident is required to fetch such information, but its a fact that such incidents bring about a good reason to explain the technology to us non involved people.
This document explains the handling of stopping of oild wells in cases of temporary abandonment. Its quite interesting to understand it.
Further, this page explains what should have happened against what happened at the deepwater horizon oil well which resulted in death of 11 people and loss of investment on the oil rig, not the forget the huge oil spill in Gulf of Mexico...
Its really unfortunate that such incidents happen, perhaps its a price we humans need to pay to tackle mother nature for resources. More than that, when I was reading a page about this on cnn, i had a feeling of, "Oh God, so much oil would be wasted in the spill, and we are already talking about scarcity of oil resources". From an estimate, more than 5000 barrels of oil is|was spilling from this rig into the sea. I dont know whether the spilling has since stopped or not, but its a huge waste nonetheless.
I hope they can find some way to contain the spill and save the environment from destruction of flora/fauna around the place due to oil spill in the sea. This would also save the precious oil.
I wish I could extract the images and post them here, inline, but there might be copyright issues.. Would lookup on wikimedia later and see if there is some information/photos about it...
Quite informative really...
Wednesday, May 5, 2010
Ubuntu 10.04 is here.... Upgrade today...
Its only been a few hours since I have had the pleasure to upgrade to the latest version of Ubuntu.
And without any doubt, or any detailed analysis/investigation I can say this much for sure -
- The upgrade process was super easy. No hassles whatsoever, you just need to have a decent internet connection, few times you need to confirm the suggested decision, and done...
- The new system looks cleaner, much much cleaner. Its neat, to some extent beautiful. Its not about the background or themes or anything like that, but the overall look and feel is genuinely cool. Perhaps its to do with one thing that I have done on my part. My system font is "Lucida Grande" all across. And, for some reason the shapes and looks on this font are far better than anyone else I have encountered.
- The boot time has come down a good notch.
Well, I guess this should be a good starting point for my review on the new version, lets see how it comes across further.
Friday, April 30, 2010
Implementing Cartesian Product in Informatica Mapping
However, when your requirements need this, there is no direct way to do it in informatica joiner transformation. Either you do it in the db side, by overriding your source qualifier sql statement and building it in there.
However, I have seen that some designers dont like to override sql statements, in such cases you'd have to implement it inside the mapping only. Here's a workaround for achieving that. Here goes -
- Read both the sources using their own source qualifiers, normally.
- For both of them, put in an Expression Transformation after the source
- In both the expression transformations, create an output port with a constant value. For Example, call it dummy1 for stream 1 and assign it a value -1. Similarly, a port would be created in the second pipeline, lets call it dummy2 and assign it a value -1.
- Now create a joiner transformation. Link ports [including the one that we created with a constant value] to the joiner from both the expressions.
- In the join condition, choose to compare the dummy columns.
- The rest of the joiner configuration would have to be like any other joiner. Nothing specific.
Before implementing the above solution, be sure to go back and check if its actually required for your application to have cartesian product !!!!
Thursday, April 29, 2010
Hard vs Soft Parse in Oracle...
So, shamelessly copying.. :)
[From AskTom]
Parsing
This is the first step in the processing of any statement in Oracle. Parsing is the act of breaking the submitted statement down into its component parts ? determining what type of statement it is (query, DML, DDL) and performing various checks on it.
The parsing process performs two main functions:
o Syntax Check: is the statement a valid one? Does it make sense given the SQL grammar documented in the SQL Reference Manual. Does it follow all of the rules for SQL.
o Semantic Analysis: Going beyond the syntax ? is the statement valid in light of the objects in the database (do the tables and columns referenced exist). Do you have access to the objects ? are the proper privileges in place? Are there ambiguities in the statement ?
For example if there are two tables T1 and T2 and both have a column X, the
query ?select X from T1, T2 where ?? is ambiguous, we don?t know which table to get X from. And so on.
So, you can think of parsing as basically a two step process, that of a syntax check to
check the validity of the statement and that of a semantic check ? to ensure the
statement can execute properly. The difference between the two types of checks are hard for you to see ? Oracle does not come back and say "it failed the syntax check", rather it returns the statement with a error code and message. So for example, this statement
fails with a syntax error:
While this statement failed with a semantic error ? if the table NOT_A_TABLE existed and we had permission to access it, this statement would have succeeded:
That is the only way to really tell the difference between a semantic and syntactic error ? if the statement COULD have executed given the proper objects and privileges, you had a semantic error, otherwise if the statement could not execute under any circumstances, you
have a syntax error. Regardless ? Oracle will not execute the statement for you!
The next step in the parse operation is to see if the statement we are currently parsing has already in fact been processed by some other session. If it has ? we may be in luck here, we can skip the next two steps in the process, that of optimization and row source generation. If we can skip these next two steps in the process, we have done what is known as a Soft Parse ? a shorter process to getting our query going. If we cannot, if we must do all of the steps, we are performing what is known as a Hard Parse ? we must parse, optimize, generate the plan for the query. This distinction is very important. When developing our applications we want a very high percentage of our queries to be Soft Parsed ? to be able to skip the optimize/generate phases ? as they
are very CPU intensive as well as a point of contention (serialization). If we have to
Hard Parse a large percentage of our queries, our system will function slowly and in some cases ? not at all.
The way this sharing of SQL in Oracle is accomplished is via the shared pool, a piece of memory in the SGA maintained by Oracle. After Oracle parses the query and it passes the syntax and semantic checks ? it will look in the shared pool component of the SGA to see if that same exact query has already been processed by another session.
Since it has performed the semantic check it has already figured out:
o Exactly what tables are involved
o That we have access to the tables (the proper privileges are there)
And so on. Now, it can look at all of the queries in the shared pool that have already been parsed/optimized and generated to see if the work has already been done.