what would put an offer from Release to Hold

If the logic is really simple (a few lines of code), it may be tempting to duplicate the code a few places rather than refactor to extract a method. A few hidden drawbacks —

1) what if the logic changes? have to change several places.

2) even if the logic rarely (never say never) changes, see the email chain below for another reason.

In the re-architecture, it may be worthwhile to have a simple façade method “changeReleaseToHold()”, so we can quickly scan the source code (in IDE or grep) to see how many places call it.

Make sure no one could easily bypass this choke point.
Please let me know in case you have a list of such rules which would make an offer go from Release to Hold.


sybase tempdb basics

1984 — first introduced. 23 years. mature.

duration — a tempdb can exist for
* one sql
* part of an sql
* a user session
* multiple sessions

There’s one default temporary database, known as “tempdb”. ASE-15 supports multiple additional temporary databases. J4? Performance.

Lock contention, specifically.

Fairchild Semicon’s IP traffic priority

Practical insight. Extremely useful to a company economizing on bandwith

Based on packet “protocol” [1], an IP router can give relative priorities to
Priority 1: voip packets
Priority 2: peoplesoft traffic
Priority 3: browser traffic
Proirity 4: lotus notes replication traffic

Lower priority packets are dropped more.

The most important browser traffic is, hold your breath, sales processing[2]. Sales staff use a web interface to process sales data. DB resides on another continent! In a rare but illustrative /incident/, lotus traffic ate into Priority 3 bandwidth and brought sales processing to a grinding slowdown.

As an alternative to a relatively fragile web interface, I suggested async messaging-based sales processing application. No clear answer.

[2] perhaps including but not limited to sales order
[1] packet headers on one layer of the envelopes

%% iview quiz #2 — pl/sql exception

Let's build a good quiz and feel confident for 2 years.

A1: zero_divide, dup_vall_on_index, invalid_number,
A3: the caller (ie caller of the pl/sql code) receives it
A2: system raise exceptions. The programmer can also raise a user-defined exception.

q1: name a few common pl/sql exceptions and how did you handle them
q3: what if you don't handle an particular type of exception? Tell me what happens?
q2: how and when can you RAISE an exception@@
q: EXCEPTION comes before or after RETURN in a function? This could appear in a paper quiz.

pl/sql q&&a non-iview

A1: No. Just an empty identifier.
q: how does an insteadof trigger support DML on any view, even non-updatable views?
a: I think this trigger can be placed on any view.

A4: erro code + erro message

q: what constitutes a pl/sql block?
A: I think BEGIN and END

A7: declare a user-defined exception, to be *raised* later
A89: I think the context surrounding the raise

q7: what is meant by declaring an exception?

q: can you connect to your oracle instance from a cybercafe and see your colleague’s pl/sql source with original comments?
A: yes see tref

q: can you obfuscate your pl/sql source?
A: yes see tref

Q: can i raise a standard exception?

q4: a pair of things to be defined for an exception, beside its name?

q: why do some say java try/catch and exception propagation borrowed from pl/sql?
A: “catch or propagate”. In other words, uncaught exceptions are propagated.

Q1: When declaring a user-defined exception, is there any content in it?

Q89: a user-defined exception usually signifies a specific (rather than vague) condition. Where is the specific condition specified?

–session as in “session object”