Hi Martijn, I spend at least 30% of my daily time "dancing with PL/SQL".

Personally I think using domains would be more "elegant". Your "table.column%TYPE"
suggestion would resolve many cases. Maybe it's not as purist as a domain (you need
to anchor your code to one specific table/column) but would be a major improvement
for writing universal PSQL blocks.

Regards,
Daniel Berstein.

On 8 Aug 2003 at 8:44, Martijn Tonies wrote:

> Daniel,
>
> > Thanks for your answer Martijn. Your points are exactly the reason why I
> think such
> > feature would be so useful, plus the added value of preserving the
> modelled bussiness
> > logic.
>
> Oh, I agree with you ... :-) ... But I guess it all makes it harder
> to create...
>
> Do you know Oracle? 'Cause it allows things like
>
> PARAM1 EMPLOYEE.EMPLOYEEDID%TYPE
>
> As a param datatype - this also helps a lot. And yes, these procedures
> are compiled as well. But when the EMPLOYEE.EMPLOYEEID
> column is changed, the procedure is flagged "invalid" and automatically
> re-compiled on the first call - it fails if the column is dropped - or you
> can have a decent developer-UI that shows you the invalid procedures
> and let's you recompile/change them.
>
> I would like to have an "invalid object" feature in Firebird. I've described
> and asked for it in IB as well:
> http://qc.borland.com/wc/wc.exe/details?reportid=5441
>
>
>
>
> With regards,
>
> Martijn Tonies
> Database Workbench - the developer tool for InterBase & Firebird
> Upscene Productions
> http://www.upscene.com
>
>
>
> To unsubscribe from this group, send an email to:
> firebird-support-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>