|Subject||Re: [Firebird-Architect] transient data sets and procedures|
> Not exactly, but close. The difference is that the transient data setCan you please give us some examples of proposed syntax and how
> has a life outside the procedure. It's created with a select statement
> - or possibly as Jim suggested with an insert/update/delete - with the
> keyword YIELDING followed by the name of the data set. The data set
> could be created in the procedure or it could be created by the
> application - or another procedure - before the procedure is invoked.
> My model would not include constraints (e.g. not null, primary key) on
> the declaration - the declaration exists only to give a physical mapping
> to a data source that is not defined at the time the procedure is created.
it can be used ? Without it i afraid i have a stupid questions ;-)