No it means that I can't spell. :-)

With respect to Python vs Perl, Python evolved from Perl and I think you'll
see a lot more python use in Linux than Perl. (python + tcl/tk) in KDE???

-Mike

__________________________________________________ _______________
Help yourself to FREE treats served up daily at the Messenger Café. Stop by
today!
http://www.cafemessenger.com/info/in...M_OctHMtagline

Its a good thing you're not running a for profit software organization.

A lot of people don't appreciate the costs in maintaining multiple ports
across multiple platforms.
Unless you can show the revenue generation against the cost, or if its done
for a strategic/marketing decision, you don't waste your money/time/effort
on a non-viable port.

We're not talking about a proof of concept port like the PS3/cell port, but
a viable released,maintained port.

If IBM is doing one, then there's a reason. And its going to have to make
money or have the expectation of making money.

__________________________________________________ _______________
Capture the missing critters!** Play Search Queries and earn great prizes.
http://club.live.com/search_queries....ltextlink1_oct

Apple just a consumer products company? Hmmm. I could comment on that, but
then I'll get shot. ;-)

As I said, Oracle would have been ported first and its been there and done
that.

So one has to ask why an Informix port? ;-)

Hint: There's a niche that Apple touches and that niche is Informix centric.
It could be that the relationship between Apple and Oracle soured a bit
because Oracle doesn't play in this niche or rather play well.

Again sorry for being a bit cryptic. ;-)

BTW, when will Oracle get their act together and do temp tables right?
Anyone who's had to suffer through their bastardized "global" temp tables
can appreciate that a *real* database allows users to create temp tables on
the fly as part of their adhoc queries.

__________________________________________________ _______________
Help yourself to FREE treats served up daily at the Messenger Café. Stop by
today!
http://www.cafemessenger.com/info/in...M_OctHMtagline

Ian Michael Gumby wrote:

You sound like my boss

But I think you're right, it hasn't just been done for people to play
around on laptops.

Ben.

Once available the Mac port is planned to be one of the freeDeveloper Edition platforms.

Guy

----- Original Message ----
From: "Gentsch, Samuel" <SAM_GENTSCH (AT) homedepot (DOT) com>
To: Guy . <gbowerman (AT) yahoo (DOT) com>; John Carlson <jwcarlson1 (AT) yahoo (DOT) com.invalid>; informix-list (AT) iiug (DOT) org
Sent: Thursday, October 18, 2007 5:08:27 AM
Subject: RE: IDS on a Mac?




WooWooo!

That rocks....

I hope they release a free Express version and put it out at all the
Universities.
I have been reading about many College stores selling more Macs than
PCs.

It would be interesting to prime the waters with IDS at that low level.

Too bad it is not feasible to con Apple to install it in Leopard as a
default software, like perl.

Sam





__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

On 18 Oct, 16:29, "Ian Michael Gumby" <im_gu... (AT) hotmail (DOT) com> wrote:

How do Oracle temp tables work? What is the problem with them?

On Oct 18, 2:20 pm, "Guy ." <gbower... (AT) yahoo (DOT) com> wrote:
I agree with Mr. Sam.....

wee hoo! (and most excellent). Sam is one of the reasons I looked into
picking up a Mac in the first place. He'd always drag his around the
IIUG board meetings and rave about it. Now I'm hooked....glad to hear
IDS is heading towards OS/X.

Mark.

david (AT) smooth1 (DOT) co.uk wrote:
In Oracle the tables are not temporary ... no need for them to be due to
the difference in locking and transaction architecture. Rather it is the
data within them that is transitory.

There are two types of temp tables in Oracle ... the first for example:

CREATE GLOBAL TEMPORARY TABLE gtt_zip2 (
zip_code VARCHAR2(5),
by_user VARCHAR2(30),
entry_date DATE)
ON COMMIT DELETE ROWS;

does precisely what the syntax indicates. The second has a different
behavior:

CREATE GLOBAL TEMPORARY TABLE gtt_zip3 (
zip_code VARCHAR2(5),
by_user VARCHAR2(30),
entry_date DATE)
ON COMMIT PRESERVE ROWS;

and empties itself at the end of a session.

The advantages of Oracle's version of temp tables relates specifically
to Oracle's use of undo segments and multiversion read consistency and
would make no sense in Informix thus I can understand the attitude. In
Oracle building Informix-type temp tables would be similarly bad design.

The OP's statement most likely stems from not understanding the
differences between the two products.
--
Daniel A. Morgan
University of Washington
damorgan@x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org

DA Morgan wrote:
Standard actually).


Here is my take:
The advantage of session-local temporary tables, that is tables who's
definition is not persisted in the catalog has the advantage that ad-hoc
tables can be created quickly without impacting the catalog and without
a care whether some other session may have a table with the same name
(but a different signature)
The downside of this behavior is that it's somewhat challenging to use
these kinds of tables across multiple objects because there is no
guarantee that the procedure that is trying to use Temp1 actually gets
Temp1 in the shape it expects it to be.
To underline the challenge SQL Server 7 had some issues there where a
procedure would happily read columns as e.g. integer that were really
varchar because the temp was dropped and recreated differently between
two invocations...

CREATED temporary tables on the other hand provide the same certainty
about the table's signature as persistent tables.
Further, because they are persistently defined there is no need to
ensure teh table is actually declared in a given session. One can just
INSERT/UPDATE/SELECT from the table. It typically gets instantiated on
first reference.
The downside is (there is always a downside...) that it's a really bad
idea to create and destroy these tables ad-hoc.

So how does Oracle get around this downside? PL/SQL collections (INDEX
BY TABLES, ...) as storage fro temporary objects, BULK COLLECT and
FORALL for INSERT and SELECT into them.

Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

Serge Rielau wrote:
Excuse me Serge but this isn't the DB2 usenet group. It's over there on
your right. This is Informix and Oracle's temp table implementation is
Oracle's.

True. But consider the improved efficiency of not running the DDL in the
first place. Consider that in Oracle the DDL is run one time during
schema creation and never run again. A substantially lower overhead than
300,000 people simultaneously connected and all running essentially
identical DDL to create 300,000 essentially identical tables. If
everyone, as in Oracle, can use the same table without any chance of
corrupting or altering another session's data no need for more than one.

With a lot of overhead running the DDL to create and then drop them.

You'll have to ask Mark. <g>

While you're at it ask him for a job. Tomorrow's forecast:
Redwood Shores 76 and sunny
Toronto 58 and raining

And it is only going to get a lot worse.
--
Daniel A. Morgan
University of Washington
damorgan@x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org