Otto Hirr (otto...@olabinc.com)

> From: Geoffrey Gowey
> Sounds reasonable, but what one manager answers today is subject to be
> changed by another tomorrow.

The intent is to get out in the open their "official" statement. That in tu=
rn may create a discussion inside Sun that may not have taken place.

If postgres community does not like the stand, then lobby to change it. Lik=
e you say, nothing either in time or by individual is forever locked in.

If the postgres community likes it, then be sure to continue to support Sun=
so that they continue in that direction. If they come out with a favorable=
strategy or had a planned strategy but kept it to themselves and postgres =
disses them, then they may take their toys and decide to play in other ways.

But get it out in the open as much as can be done. Simple. Then you know wh=
ere they stand/don't-stand/or remain mute.

Then you can take further action.

Rumors/opinions are just that.

Postgres needs to have an "official spokesman" make a request at a "very im=
portant top official" that is responsible for the acquisition.

..Otto

> Russ Brown wrote:
> > http://blogs.mysql.com/kaj/sun-acquires-mysql.html/
> >
> > What does this mean for Sun's support of Postgres?
> >

So why not go directly to the "source", Sun itself, and ask them?

Someone like Bruce should just knock on the door and ask.

Then you can evaluate the answer. Either a lie, the truth, or somewhere
in-between, and the answer may only have a certain "shelf-life", for what is
true today in the tech industry is false later.

..Otto

Greetings,

I have several tables with relationships between them.
All tables are to have some attributes such as
created_by, created_on, modified_by, etc.

If I turn on 'all' in MethodMaker, it will attempt to
create lookup_columns between related tables, including
items like those listed above. Only certain columns should be
used as lookup_columns, but not others.

Furthermore MethodMakers complains about (as example):

MethodMaker: Creating lookup_columns method
MyApp::Data::Row::event->modified_on \
  will override the method of the same name in the parent class
MethodMaker: skipping lookup_columns method
MyApp::Data::Row::event->modified_on \
  subroutine already exists.

Question, I want to use 'all' for MethodMaker as a general rule,
but then create exceptions...

How can this be done, or am I missing something.

Regards,

..Otto

Greetings,

I've turned on sql debug and simply insert a few records into a table.
It seems that sql is being generated to pre-query for uniqueness on
unique fields... and I have referential_integrity =0.

Is this right? Is there a pre-query being done? I have yet to step
through the code...

..Otto

in looking at some of the messages, i see at bottom something to the effect
of "2 messages have been excluded from this view by a project administrator"

i had an idea for one of the problems someone presented but then was
wondering if other peoples responses (but not readable) had already answered
the issue...?