Re: null indicators....

On Sep 17, 2:21 pm, jerseyca..._at_gmail.com wrote:
> We have a code generation process which spits out a tremendous amount
> of data loading code. We selectively add indicators to these table
> fields based on certain criteria, such as data type, nullablility,
> etc.
>
> Question is, is their any harm in giving every field an indicator,
> regardless of type and/or attributes?
>
> We have a problem lately with mismatching database schemas and
> software releases, and doing this would help with that problem. It
> would also simplify the code generation tool too ;)
>
> Thanks,
> AJ

You really should give:
Oracle version
Programming language (specific to this case) Platform (OS at least)

I ASSUME (now don't make us both fit the saying about that word!) that you are talking about generating Pro*C or other Pro*language. In that case, it would do no harm to have indicators for all the host variables. Well there is just the overhead of the additional memory and the code to check each indicator. Putting indicators on the variables being loaded from Primary key columns is somewhat overkill, but again, it doesn't hurt.

Now finally if this was a Pro*C question it really should have gone to the .tools group.

So get back to us on what you were really asking.   Ed Received on Tue Sep 18 2007 - 07:29:26 CDT