2010/3/11 Gerhard Heift :
> On Thu, Mar 11, 2010 at 08:38:46AM -0800, Chris Travers wrote:
>> > On 3/10/2010 11:52 PM, Chris Travers wrote:
>> > Which
>> > i'm at a loss why nesting would help solve any problem what so ever. I
>> > imagine the search path on some connections would be all inclusive
On Thu, Mar 11, 2010 at 08:38:46AM -0800, Chris Travers wrote:
> > On 3/10/2010 11:52 PM, Chris Travers wrote:
> > Which
> > i'm at a loss why nesting would help solve any problem what so ever. I
> > imagine the search path on some connections would be all inclusive so
> > ambiguous names is not s
> On 3/10/2010 11:52 PM, Chris Travers wrote:
>>
>> There are two major limitations here of schemas:
>>
>> 1) They can't be nested leading again to possible namespace ambiguity.
>> 2) there are a number of requests to try to get the application to
>> install into an arbitrary, nonpublic schema.
>
On 3/10/2010 11:52 PM, Chris Travers wrote:
>
> There are two major limitations here of schemas:
>
> 1) They can't be nested leading again to possible namespace ambiguity.
> 2) there are a number of requests to try to get the application to
> install into an arbitrary, nonpublic schema.
>
> If sc
On Wed, Mar 10, 2010 at 7:08 PM, Justin Graf wrote:
> look into schemas.
>
> this allow group table and procedure logically and can limit access
> based on schemas.
>
> what i did is group procedures, views, and tables into schemas to keep
> them logically grouped.
> in one project there is 300
On 3/10/2010 8:16 PM, Chris Travers wrote:
> Hi all;
>
> One of my applications currently has over 60 stored procedures and
> future versions will likely have several hundred. I am wondering what
> folks find to be helpful naming conventions for managing a large
> number of stored procedures. We
Hi all;
One of my applications currently has over 60 stored procedures and
future versions will likely have several hundred. I am wondering what
folks find to be helpful naming conventions for managing a large
number of stored procedures. We tried using double underscores to
separate module vs p
