Hello Barbara,
> ... and that's exactly what I did, once I found the TRIM description in
> the HSQLDB documentation. (You may not have seen my note about that,
in fact I missed it, sorry.
> So I can see that the argument could be left out, but how does it
> identify which possibility is the de
Frank Schönheit - Sun Microsystems Germany wrote:
Hello Barbara,
Hmm. In the Execute SQL Statement dialog, I had
UPDATE "Addresses" SET ADDR = TRIM ( ADDR )
What I got was an error:
2: Unexpected token in statement [UPDATE "Addresses" SET ADDR = TRIM ( ADDR]
Note that it seems to have dr
Frank Schönheit - Sun Microsystems Germany wrote:
So, the complete syntax if you want to use TRIM is
UPDATE "Addresses" SET ADDR = TRIM ( BOTH FROM ADDR )
where you can even omit the BOTH.
Ciao
Frank
Almost. TRIM( FROM ) works in SQL View, but not in Designer View.
It generates a warni
Hello Barbara,
> Hmm. In the Execute SQL Statement dialog, I had
> UPDATE "Addresses" SET ADDR = TRIM ( ADDR )
>
> What I got was an error:
> 2: Unexpected token in statement [UPDATE "Addresses" SET ADDR = TRIM ( ADDR]
>
> Note that it seems to have dropped the closing paren, and the preceding
Hi Barbara,
> About these bugs - do I need to upgrade to 2.2.1, or the latest
> development 2.3, and see whether they exist there before documenting the
> issues?
That would be helpful. I don't think any of those issues already exists,
but I might be wrong. In this case, you would save a few pe
Frank Schönheit - Sun Microsystems Germany wrote:
Hello Barbara,
Thanks for the explanation, Frank. This modality is pretty confusing for
somebody who's used to "update queries" from that other program! Maybe
the doc should all make it clear that the Designer is only for SELECT
commands
Hello Barbara,
> Thanks for the explanation, Frank. This modality is pretty confusing for
> somebody who's used to "update queries" from that other program! Maybe
> the doc should all make it clear that the Designer is only for SELECT
> commands (nothing else produces a result set, right?), and
Am Freitag, den 24.08.2007, 08:07 -0500 schrieb Barbara Duprey:
> Should the addition of
> leading and trailing blanks for copies from Writer be considered a bug,
> or is changing that an RFE?
http://www.openoffice.org/issues/show_bug.cgi?id=80916
and the other one you can omit:
http://www.op
Frank Schönheit - Sun Microsystems Germany wrote:
Hello Barbara,
When I tried this as a query, that didn't work either:
SQL Status: 0
Error code: -155
Statement does not generate a result set
Just as explanation, as you already found your way:
This message says you executed t
Hello Barbara,
> When I tried this as a query, that didn't work either:
>
> SQL Status: 0
> Error code: -155
>
> Statement does not generate a result set
Just as explanation, as you already found your way:
This message says you executed the statement in the query designer. The
designer is
andrew wrote:
Hmm. In the Execute SQL Statement dialog, I had
UPDATE "Addresses" SET ADDR = TRIM ( ADDR )
Hi Barbara,
I believe it was Mr Reagan that said - 'Trust but verify."
Out of the box HSQL has
LTRIM = Left Trim
RTRIM = Right Trim
But no TRIM... if you could see how hard I am l
Am Donnerstag, den 23.08.2007, 18:46 -0500 schrieb Barbara Duprey:
>
> Marc Santhoff wrote:
> > Am Donnerstag, den 23.08.2007, 16:42 -0500 schrieb Barbara Duprey:
> >
> >
> >> OK, I saw in the Help that only admin commands are allowed in the
> >> Execute SQL Statement dialog, so I created a qu
Hmm. In the Execute SQL Statement dialog, I had
UPDATE "Addresses" SET ADDR = TRIM ( ADDR )
Hi Barbara,
I believe it was Mr Reagan that said - 'Trust but verify."
Out of the box HSQL has
LTRIM = Left Trim
RTRIM = Right Trim
But no TRIM... if you could see how hard I am laughing right now
Marc Santhoff wrote:
Am Donnerstag, den 23.08.2007, 16:42 -0500 schrieb Barbara Duprey:
OK, I saw in the Help that only admin commands are allowed in the
Execute SQL Statement dialog, so I created a query. Same result, except
that the whole statement is there. So what token is it complain
Am Donnerstag, den 23.08.2007, 16:42 -0500 schrieb Barbara Duprey:
> OK, I saw in the Help that only admin commands are allowed in the
> Execute SQL Statement dialog, so I created a query. Same result, except
> that the whole statement is there. So what token is it complaining about?
>
> SQL St
Barbara Duprey wrote:
andrew wrote:
Barbara,
I sure don't feel preached at, just informed. Would you by any
chance know the SQL to remove leading and trailing blanks from
FIELDA in TABLEB? I'm sure it's all somewhere in there, but I can't
face that learning curve right now!
UPDATE TA
andrew wrote:
Barbara,
I sure don't feel preached at, just informed. Would you by any chance
know the SQL to remove leading and trailing blanks from FIELDA in
TABLEB? I'm sure it's all somewhere in there, but I can't face that
learning curve right now!
UPDATE TABLEB SET FIELDA = TRIM( F
andrew wrote:
Barbara,
I sure don't feel preached at, just informed. Would you by any chance
know the SQL to remove leading and trailing blanks from FIELDA in
TABLEB? I'm sure it's all somewhere in there, but I can't face that
learning curve right now!
UPDATE TABLEB SET FIELDA = TRIM( F
Barbara,
I sure don't feel preached at, just informed. Would you by any chance
know the SQL to remove leading and trailing blanks from FIELDA in
TABLEB? I'm sure it's all somewhere in there, but I can't face that
learning curve right now!
UPDATE TABLEB SET FIELDA = TRIM( FIELDA )
Because
andrew wrote:
Well, I didn't mean to get into a preaching mode there, and am afraid
I somewhat did.
Oops -- ignore my last message, just looked at yours again and saw
Say you have a table named t1 and a column c1 the column contains
records with erroneous leading or trailing spaces, now yo
andrew wrote:
Well, I didn't mean to get into a preaching mode there, and am afraid
I somewhat did.
I sure don't feel preached at, just informed. Would you by any chance
know the SQL to remove leading and trailing blanks from FIELDA in
TABLEB? I'm sure it's all somewhere in there, but I ca
Well, I didn't mean to get into a preaching mode there, and am afraid I
somewhat did.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
andrew wrote:
Barbara Duprey wrote:
... seems to be built around confining all edits to a single field in
a single record at any given time. No Find and Replace, for instance,
which would have been a great help in dealing with those leading and
trailing blanks. ..
Well, leaving with what
Barbara Duprey wrote:
... seems to be built around confining all edits to a single field in
a single record at any given time. No Find and Replace, for instance,
which would have been a great help in dealing with those leading and
trailing blanks. ..
Well, leaving with what GUI features are
andrew wrote:
Hi Barbara,
I wasn't gong to send another email on this thread again tonight -
but.since this one just arrived.
I read over your earlier message, with the numbered issues a couple of
times, and had a few more comments. Mostly dealing with some of the
features for data exchan
Frank Schönheit - Sun Microsystems Germany wrote:
Hi Barbara,
Yes, that was the specific question (let's call it Issue 1). In this
case, it would be complicated by the fact that Base did not define the
PK it generated for the original .dbf import as auto-increment.
This would be an
andrew wrote:
Barbara Duprey wrote:
andrew wrote:
Barbara Duprey wrote:
Ah, yes. I'd still prefer this to be done automatically when the data
exceeded the field capacity, perhaps after verification that this is
what's wanted, but I'm glad the new version will at least allow the
redefiniti
Hi Barbara,
> Yes, that was the specific question (let's call it Issue 1). In this
> case, it would be complicated by the fact that Base did not define the
> PK it generated for the original .dbf import as auto-increment.
This would be an RFE (request for enhancement) in IZ, to have an option
t
Barbara Duprey wrote:
andrew wrote:
Barbara Duprey wrote:
Ah, yes. I'd still prefer this to be done automatically when the data
exceeded the field capacity, perhaps after verification that this is
what's wanted, but I'm glad the new version will at least allow the
redefinition without data d
Hi Barbara,
I wasn't gong to send another email on this thread again tonight -
but.since this one just arrived.
I read over your earlier message, with the numbered issues a couple of
times, and had a few more comments. Mostly dealing with some of the
features for data exchange between Base /
andrew wrote:
Barbara Duprey wrote:
I'd have thought that "VARCHAR" would automatically expand as needed
up to at least 255, but it doesn't, and the field definitions cannot
be modified in place. The option is presented to delete the field and
append a new one as redefined, but that discards
Hi Marc,
> This is issue 80917.
> ...
> And this one is issue 80916
Thanks and thanks.
Ciao
Frank
--
- Frank Schönheit, Software Engineer [EMAIL PROTECTED] -
- Sun Microsystems http://www.sun.com/staroffice -
- OpenOffice.org Base http://dba.op
andrew wrote:
Barbara Duprey wrote:
(Comments in message)
Yes, that was the specific question (let's call it Issue 1). In this
case, it would be complicated by the fact that Base did not define
the PK it generated for the original .dbf import as auto-increment.
This one has a work arou
andrew wrote:
I closed up SO8 and started up OOo2.3m_1 to check that copy paste to
Calc again
I can copy a range of cells in an Access dataview and paste them into
a Calc sheet.
I can not drag and drop a table object from Acess to a Calc sheet. -
Frank Schönheit - Sun Microsystems Germany wrote:
Hi Barbara,
Your idea sounds somewhat unusual for a database (in which situations,
for instance, would you want to copy a rectangular portion to a location
starting at another column? How often, really, does one have data where
this makes sense?)
Am Dienstag, den 21.08.2007, 04:15 +0200 schrieb Marc Santhoff:
> > > Okay, missing first columns on copy and paste would be worth an issue
> >
> > Definitely.
>
> I'm in preparation of writing it. There seems to be an off-by-one error
> somewhere in the pasting code, the first line is missing wh
Barbara Duprey wrote:
I'd have thought that "VARCHAR" would automatically expand as needed
up to at least 255, but it doesn't, and the field definitions cannot
be modified in place. The option is presented to delete the field and
append a new one as redefined, but that discards all the data. (I
Barbara Duprey wrote:
(Comments in message)
Yes, that was the specific question (let's call it Issue 1). In this
case, it would be complicated by the fact that Base did not define the
PK it generated for the original .dbf import as auto-increment.
This one has a work around.
If you drag
(Comments in message)
Frank Schönheit - Sun Microsystems Germany wrote:
Hi Barbara,
Are you (or is anybody else lurking here) aware of an issue for this? If
not - Barbara or Marc, care to submit one? I mean, there should be a
direct way, shouldn't it?
I'd be glad to submit an issu
Am Montag, den 20.08.2007, 21:56 +0200 schrieb Frank Schönheit - Sun
Microsystems Germany:
> Hi Marc,
>
> > Since transferring data from writer tables into base does work there is
> > a direct way (sort of). If there would be (is there?) a corresponding
> > help entry that is easily found it woul
Hi Marc,
> Since transferring data from writer tables into base does work there is
> a direct way (sort of). If there would be (is there?) a corresponding
> help entry that is easily found it would be fine IMHO. If it should be
> really easy for the average user a step-by-step helper dialog would
Hi Barbara,
>> Are you (or is anybody else lurking here) aware of an issue for this? If
>> not - Barbara or Marc, care to submit one? I mean, there should be a
>> direct way, shouldn't it?
>>
> I'd be glad to submit an issue if there isn't one. My idea of how it
> should work would extend the
Am Sonntag, den 19.08.2007, 19:08 -0500 schrieb Barbara Duprey:
> Frank Schönheit - Sun Microsystems Germany wrote:
> > Hi Marc,
> >
> >
> >> As the last time I answered my recommendation is OO.o-Calc.
> >>
> >
> > Are you (or is anybody else lurking here) aware of an issue for this? If
>
Hello Frank,
Am Sonntag, den 19.08.2007, 21:50 +0200 schrieb Frank Schönheit - Sun
Microsystems Germany:
> Hi Marc,
>
> > As the last time I answered my recommendation is OO.o-Calc.
>
> Are you (or is anybody else lurking here) aware of an issue for this?
Not really, currently I'm not digging
Frank Schönheit - Sun Microsystems Germany wrote:
Hi Marc,
As the last time I answered my recommendation is OO.o-Calc.
Are you (or is anybody else lurking here) aware of an issue for this? If
not - Barbara or Marc, care to submit one? I mean, there should be a
direct way, shouldn't
Hi Marc,
> As the last time I answered my recommendation is OO.o-Calc.
Are you (or is anybody else lurking here) aware of an issue for this? If
not - Barbara or Marc, care to submit one? I mean, there should be a
direct way, shouldn't it?
Thanks & Ciao
Frank
--
- Frank Schönheit, Software Eng
Marc Santhoff wrote:
Am Freitag, den 17.08.2007, 11:33 -0500 schrieb Barbara Duprey:
Marc, as I mentioned the data was already in Writer tables (with
everything but the key). And I didn't actually use the via-Calc solution
last time, because of the data integrity issues I would have had .
Am Freitag, den 17.08.2007, 11:33 -0500 schrieb Barbara Duprey:
> Marc, as I mentioned the data was already in Writer tables (with
> everything but the key). And I didn't actually use the via-Calc solution
> last time, because of the data integrity issues I would have had . For
> instance, some
Marc Santhoff wrote:
Am Mittwoch, den 15.08.2007, 15:00 -0500 schrieb Barbara Duprey:
I have a database (embedded) with a table and a number of queries. When
I created the table by copying a table from another database, I
specified that a primary key should be created, so each record acqui
Am Mittwoch, den 15.08.2007, 15:00 -0500 schrieb Barbara Duprey:
> I have a database (embedded) with a table and a number of queries. When
> I created the table by copying a table from another database, I
> specified that a primary key should be created, so each record acquired
> a unique number
I have a database (embedded) with a table and a number of queries. When
I created the table by copying a table from another database, I
specified that a primary key should be created, so each record acquired
a unique number. Now I've gotten to a point where I want to add records.
Ideally, I cou
51 matches
Mail list logo
