db-torque-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Duddikunta, Padmanabha" <P...@cdc.gov>
Subject RE: Schema qualifier for table names
Date Tue, 17 Jun 2003 17:26:31 GMT
I don't think torque.database.schema is doing anything other than
identifying schema for JDBC task.  When using torque (I mean when using
torque to access the database in your application via OM) you probably are
using aliases or you have some other mechanism in place.

Thanks
Paddy



-----Original Message-----
From: Ramesh Sabeti [mailto:rs@reazon.com] 
Sent: Tuesday, June 17, 2003 12:17 PM
To: 'Turbine Torque Users List'
Subject: RE: Schema qualifier for table names

My database contains multiple schemas.  In torque.properties I set the
values according to the schema in question.  I'm testing accessing
multiple schemas in a single application now.

> -----Original Message-----
> From: Duddikunta, Padmanabha [mailto:Pkd2@cdc.gov]
> Sent: Monday, June 16, 2003 2:33 PM
> To: 'Turbine Torque Users List'
> Subject: RE: Schema qualifier for table names
> 
> What do you when there are more than one schema in the database.
> 
> 
> -----Original Message-----
> From: Ramesh Sabeti [mailto:rs@reazon.com]
> Sent: Monday, June 16, 2003 5:03 PM
> To: 'Turbine Torque Users List'
> Subject: RE: Schema qualifier for table names
> 
> I don't know how it works in your app.  I use torque.properties in my
> app which includes that info.
> 
> > -----Original Message-----
> > From: Duddikunta, Padmanabha [mailto:Pkd2@cdc.gov]
> > Sent: Monday, June 16, 2003 10:28 AM
> > To: 'Turbine Torque Users List'
> > Subject: RE: Schema qualifier for table names
> >
> > See that is the problem.  Then how would it able to generate sql
with
> > schema
> > name qualifier.
> >
> > Ex:  SELECT COL1, COL2, COL3 FROM SCHEMA_NAME.TABLE
> >
> > Thanks
> > Paddy
> >
> >
> > -----Original Message-----
> > From: Ramesh Sabeti [mailto:rs@reazon.com]
> > Sent: Monday, June 16, 2003 1:13 PM
> > To: 'Turbine Torque Users List'
> > Subject: RE: Schema qualifier for table names
> >
> > Here it is.  There's no mention of the schema name in my schema.xml
by
> > the way.
> >
> >   <?xml version="1.0" ?>
> >   <!DOCTYPE database (View Source for full doctype...)>
> >  <!--  Autogenerated by JDBCToXMLSchema!
> >   -->
> >  <database defaultIdMethod="none" defaultJavaType="primitive"
> > defaultJavaNamingMethod="underscore" heavyIndexing="false">
> >  <table name="ACCESSREQUEST" idMethod="null" skipSql="false"
> > abstract="false">
> >   <column name="ARQ_ID" primaryKey="true" required="true" size="22"
> > type="DECIMAL" autoIncrement="false" inheritance="false" />
> >   <column name="MBR_ID" size="22" type="DECIMAL" primaryKey="false"
> > required="false" autoIncrement="false" inheritance="false" />
> >
> > > -----Original Message-----
> > > From: Duddikunta, Padmanabha [mailto:Pkd2@cdc.gov]
> > > Sent: Monday, June 16, 2003 9:56 AM
> > > To: 'Turbine Torque Users List'
> > > Subject: RE: Schema qualifier for table names
> > >
> > > Ramesh,
> > >
> > > Would you mind posting a portion of your generated XML schema.
> > Especially
> > > I
> > > am interested in seeing the following.
> > >
> > > <database name="ehaz" ..........................................>
> > > <table name="SITE" javaName="Site" idMethod="none">
> > >     <column name="SITE_ID" javaName="SiteId" required="true"
> > > type="VARCHAR"
> > > size="12" />
> > >     <column name="SUPERFUND_NUM" javaName="SuperfundNum"
> > required="false"
> > > type="VARCHAR" size="7" />
> > >     <column name="ATS_STATUS" javaName="AtsStatus" required="true"
> > > type="VARCHAR" size="1" />
> > > .
> > > .
> > > .
> > >
> > >
> > > Thanks
> > > Paddy
> > >
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: Ramesh Sabeti [mailto:rs@reazon.com]
> > > Sent: Monday, June 16, 2003 12:50 PM
> > > To: 'Turbine Torque Users List'
> > > Subject: RE: Schema qualifier for table names
> > >
> > > I'm generating the XML Schema directly from the database.  Maybe
you
> > > need to qualify table names in your SQL file with "XYZ." To avoid
> the
> > > default qualifier of user name "dbuser."
> > >
> > > > -----Original Message-----
> > > > From: Duddikunta, Padmanabha [mailto:Pkd2@cdc.gov]
> > > > Sent: Monday, June 16, 2003 9:40 AM
> > > > To: 'Turbine Torque Users List'
> > > > Subject: RE: Schema qualifier for table names
> > > >
> > > > I generated my XML schema from a SQL file.  I don't see anything
> > > > corresponding to schema qualifier in the generated XML schema.
> > > >
> > > > -----Original Message-----
> > > > From: Ramesh Sabeti [mailto:rs@reazon.com]
> > > > Sent: Monday, June 16, 2003 12:33 PM
> > > > To: 'Turbine Torque Users List'
> > > > Subject: RE: Schema qualifier for table names
> > > >
> > > > This is what I use for Oracle in torque.build:
> > > >
> > > > torque.database.schema=XYZ
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Duddikunta, Padmanabha [mailto:Pkd2@cdc.gov]
> > > > > Sent: Monday, June 16, 2003 9:22 AM
> > > > > To: 'torque-user@db.apache.org'; 'torque-dev@db.apache.org'
> > > > > Subject: Schema qualifier for table names
> > > > >
> > > > > I having trouble specifying schema qualifier for tables.  I
> login
> > to
> > > > > database using a user "dbuser", but my tables lie under a
> > different
> > > > schema
> > > > >
> > > > > say XYZ schema.
> > > > >
> > > > >
> > > > >
> > > > > Now I want to query XYZ.TABLE1.  But torque seems to generate
> sql
> > > > > something
> > > > > like,
> > > > >
> > > > >
> > > > >
> > > > > SELECT COL1, COL2, COL3 FROM dbuser.TABLE1   instead of
> > > > >
> > > > >
> > > > >
> > > > > SELECT COL1, COL2, COL3 FROM XYZ.TABLE1
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > I would appreciate any pointer on solving this problem.
> > > > >
> > > > >
> > > > >
> > > > > Thanks
> > > > >
> > > > > Paddy
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> >
---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> > > > For additional commands, e-mail: torque-user-help@db.apache.org
> > > >
> > > >
> >
---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> > > > For additional commands, e-mail: torque-user-help@db.apache.org
> > >
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> > > For additional commands, e-mail: torque-user-help@db.apache.org
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> > > For additional commands, e-mail: torque-user-help@db.apache.org
> >
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> > For additional commands, e-mail: torque-user-help@db.apache.org
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> > For additional commands, e-mail: torque-user-help@db.apache.org
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-user-help@db.apache.org
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-user-help@db.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org

Mime
View raw message