Re: Default schema/library for CREATE TABLE

[Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>]

No, not so much.  SQL naming breaks everything (because it uses some 
other default based on my user profile) and doesn't even check the 
library list for my files.  So I'm stuck here.

At the end of the day, I can go back and change the current library as 
Dave suggested (because that works fine), but I'd really like to 
understand why it doesn't work as I expected.



On 8/20/2019 3:27 PM, Joe Pluta wrote:
> Betcha it's something to do with system naming vs SQL naming, and 
> something I have to set on my options statement.  How much ya wanna bet?
>
> On 8/20/2019 3:25 PM, Joe Pluta wrote:
> > Okay, this one has me scratching my head.
> >
> > I've always used a prepared statement to create tables, but I wanted 
> > to try using the current schema this time.  Basically I'm creating a 
> > summary table for extract, and I wanted to it like this:
> >
> > SET SCHEMA = :newSchema;
> > CREATE TABLE NEWTABLE AS (SELECT ...) WITH DATA;
> > SET SCHEMA = DEFAULT;
> >
> > This seems pretty straightforward.  When I do it in STRSQL and 
> > hardcode the library name, everything works fine.  But when I do this 
> > in an embedded SQL program the file is always created in QGPL.
> >
> > I went so far as to do this:
> >
> > SET SCHEMA = :newSchema;
> > SET :curSchema = CURRENT_SCHEMA;
> > CREATE TABLE NEWTABLE AS (SELECT ...) WITH DATA;
> > SET SCHEMA = DEFAULT;
> >
> > I thought maybe the current schema was getting reset somehow, but the 
> > variable curSchema ends up with the same value as newSchema. But the 
> > new table still ends up in QGPL.
> >
> > Any idea what I'm missing?