Re: SCHEMAS and procedures,...



>
> > > Hi all!
> > >
> > > At the moment, the SCHEMA_PROCS does not return the IN(s) and OUT data types.
> > > As I understand it, it is supposed to be implemented by another SCHEMA. I
> > > would prefer
> > > that the SCHEMA_PROCS also return all those data types (it would be easier to
> > > code and
> > > maybe faster when querying a lot of functions). What's your opinion on this?
> > >
> >
> > Please decide between Stephan and you, to see what's the best way, but I'd vote,
> > as I said before, for a separate schema returning all these parameters:
> >
> > param    direction(in,out,inout)    type ....
> >
> > This will continue with the current design, one schema to return list of objects
> > for one type, and another for describing a specific object.
>
> I was reluctant for this SCHEMA because it means for me to find a way to
> deliver to the client information as if it were the result of a query when it
> is not: I can't have a query return the in/ou/inout (BTW how do you have INOUT
> params?) parameters in postgres, so I need to do more design and code.
>

I don't know if it's possible in postgres, oracle or MySQL, but it may be possible in
another RDBMS (??). But really, do not feel like I'm not accepting this proposal, as I
said let's see what Stephan says.




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]