hi Frank,
Am Freitag 15 April 2005 11.10 schrieb Frank Schönheit - Sun
Microsystems, Inc.:
> >>>Strange, all other statements accept strings with mixed case
> >>
> >>which ones do?
> >
> > things like 'getByName' (and not all SQL - Satements?)
>
> Ah, okay, getByName is on a level completely dif
Hi Wolfgang,
>>but don't forget to clean it up later on, to not leak resources:
>> oConnection.close()
> normally used :-))
good to hear :). This is often forgotton, which then leads to later
operations possibly failing, since the previous (still alive) connection
locks resources associated with
hi Frank,
Am Freitag 15 April 2005 09.15 schrieb Frank Schönheit - Sun
Microsystems, Inc.:
> Hi Wolfgang,
> > 3. Failed query 2: Two visual identical querys, one created
> > with the wizard, the other with basic share not the same result
>
> If "visually identically" means "identically when opene
hi Frank,
Am Freitag 15 April 2005 09.13 schrieb Frank Schönheit - Sun
Microsystems, Inc.:
> Hi Wolfgang,
>
> > Writing
> >
> > oQuery.Command = "SELECT * FROM " & "Journal"
> > the table (also all other names) was not found.
>
> with
> sQuoteChar = oConnection.getMetaData().getIdentifi
Hi Wolfgang,
> 2. Failed query 1: The MsgBox write the table identifier in Capitals
> followed by the chosen name in mixed Upper/lower case:
> The query is working after renaming the table name in ALL CAPITALS.
It seems that our engine, HSQLDB, is indeed automatically capitalizing
all identifier
Hi Wolfgang,
> Writing
>
> oQuery.Command = "SELECT * FROM " & "Journal"
> the table (also all other names) was not found.
with
sQuoteChar = oConnection.getMetaData().getIdentifierQuoteString
try adding the |sQuoteChar| before and after the table name.
If you don't have a connect
Am Dienstag 12 April 2005 10.43 schrieb Frank Schönheit - Sun
Microsystems, Inc.:
> Hi Josh,
>
> > Well, all quoted identifiers is fine *if* the identifiers come
> > from the database, not from the user. And provided that they
> > don't get automatically uppercased before being quoted.
>
> I'm n
Hi Josh,
> Well, all quoted identifiers is fine *if* the identifiers come from the
> database, not from the user. And provided that they don't get automatically
> uppercased before being quoted.
I'm not sure whether I understood Wolfgang's original post right (it
seems that two non-native Eng
Frank,
> as always, "Trying to be on the safe side, making more DBs happy than
> harming others". Or so. If the database (its driver, more precise) tells
> OOo that there *is* a quoting character for identifiers, then OOo will
> use it.
Well, all quoted identifiers is fine *if* the identifiers co
Hi Josh,
> What's the logic behind the query tool generating all-quoted identifiers?
as always, "Trying to be on the safe side, making more DBs happy than
harming others". Or so. If the database (its driver, more precise) tells
OOo that there *is* a quoting character for identifiers, then OOo wi
People:
> With Base tool 'Querys' created:
> SELECT "idJour", "vonKto" FROM "JOUR" "JOUR" WHERE ( ( "vonKto" =
> 'KASSE' ) )
> This select the data.
> Twice "JOUR" ? Strange, but works.
> All >"< in SQL are unnecessary, the system generates all (the first
> comfort in this hard job).
What's the l
Hi,
All tables now created with uppercase names and with new release
1.9.91-1.
With Base tool 'Querys' created:
SELECT "idJour", "vonKto" FROM "JOUR" "JOUR" WHERE ( ( "vonKto" =
'KASSE' ) )
This select the data.
Twice "JOUR" ? Strange, but works.
All >"< in SQL are unnecessary, the system gene
Am Sa, den 09.04.2005 schrieb Wolfgang Schaible um 22:17:
> Am Samstag 09 April 2005 21.35 schrieb Marc Santhoff:
> > Am Sa, den 09.04.2005 schrieb Wolfgang Schaible um 20:51:
> > > Hi,
> > >
> > > Have table names (UpperLower chars mixed) defined with the tool
> > > 'Base', used in Queries and For
Am Samstag 09 April 2005 21.35 schrieb Marc Santhoff:
> Am Sa, den 09.04.2005 schrieb Wolfgang Schaible um 20:51:
> > Hi,
> >
> > Have table names (UpperLower chars mixed) defined with the tool
> > 'Base', used in Queries and Forms w/o problems. Was happy.
> >
> > Writing
> >
> > oQuery.Co
Am Samstag 09 April 2005 20.51 schrieb Wolfgang Schaible:
> Hi,
>
> Have table names (UpperLower chars mixed) defined with the tool
> 'Base', used in Queries and Forms w/o problems. Was happy.
>
> Writing
>
> oQuery.Command = "SELECT * FROM " & "Journal"
> the table (also all other nam
Am Sa, den 09.04.2005 schrieb Wolfgang Schaible um 20:51:
> Hi,
>
> Have table names (UpperLower chars mixed) defined with the tool
> 'Base', used in Queries and Forms w/o problems. Was happy.
>
> Writing
>
> oQuery.Command = "SELECT * FROM " & "Journal"
> the table (also all other
Hi,
Have table names (UpperLower chars mixed) defined with the tool
'Base', used in Queries and Forms w/o problems. Was happy.
Writing
oQuery.Command = "SELECT * FROM " & "Journal"
the table (also all other names) was not found.
Strange, all other statements accept strings with
17 matches
Mail list logo
