But what would be the benefit instead of just appending it?
We are save from file format changes of HSQLDB. For example, the
format from version 1.6 is different from version 1.7 You didn't
notice because I converted the file back then ;-)
Aaahhh... ok!
Sure then let's use the hsqldb script to
On 13.Mar.2003 -- 02:44 PM, Torsten Curdt wrote:
>
>
> >That was not my understanding from Chris's email. By "has to happen at
> >runtime" do you mean because of the nature of the hsql call, or some
> >other logical constraint? I understood him to mean that the call would
> >cause hsql to pa
That was not my understanding from Chris's email. By "has to happen at
runtime" do you mean because of the nature of the hsql call, or some
other logical constraint? I understood him to mean that the call would
cause hsql to parse and run that script at build time, and shut
immediately down
At 08:28 AM 3/13/2003, Torsten wrote:
It seems wrong to put it in the hsql block (because it's specific to the
db samples). So I guess in the db block. That makes the hsql block
build (presuming that's where the hsql script call goes) depend on the
database block, which is fine as you point
It seems wrong to put it in the hsql block (because it's specific to the
db samples). So I guess in the db block. That makes the hsql block
build (presuming that's where the hsql script call goes) depend on the
database block, which is fine as you point out.
Agreed - but I am really not in f
At 08:01 AM 3/12/2003, I wrote:
At 06:24 AM 3/12/2003, Torsten wrote:
Ok, team, I fixed the esql samples. Please try.
--
Torsten
Excellent - I'll check it out tonight (which depending on where you live
is probably in the wee hours of the AM).
Tried them and they are indeed back in action,
At 03:44 AM 3/13/2003, Christian wrote:
On 12.Mar.2003 -- 01:58 PM, Geoff Howard wrote:
> At 11:23 AM 3/12/2003, Torsten wrote:
> >
> >
> >>>But the .script file *is* actually a simple .sql script.
> >>Yes, but as I remember it, wouldn't be appropriate to use as the
> >>source in other DB's, but...
On 12.Mar.2003 -- 01:58 PM, Geoff Howard wrote:
> At 11:23 AM 3/12/2003, Torsten wrote:
> >
> >
> >>>But the .script file *is* actually a simple .sql script.
> >>Yes, but as I remember it, wouldn't be appropriate to use as the
> >>source in other DB's, but...
I think the main point is that we shou
At 11:23 AM 3/12/2003, Torsten wrote:
But the .script file *is* actually a simple .sql script.
Yes, but as I remember it, wouldn't be appropriate to use as the
source in other DB's, but...
Can you remember why? I haven't really looked closer into it.
Well, it was the stuff like:
GRANT ALL ON CLA
But the .script file *is* actually a simple .sql script.
Yes, but as I remember it, wouldn't be appropriate to use as the
source in other DB's, but...
Can you remember why? I haven't really looked closer into it.
Now that the samples are at least working again, how about considering
some options
At 08:46 AM 3/12/2003, Torsten wrote:
That's why I wouldn't give up too easily on making the db setup work
from a normal sql script. Currently we have the .sql out there, but
I'm not sure it's up to date (though it looks like it), and if it's
not used, it's certainly in danger of getting out of d
On 12.Mar.2003 -- 08:23 AM, Geoff Howard wrote:
> At 03:39 AM 3/12/2003, you wrote:
> >Well, the idea was to make it easy to switch to $MY_FAVOURITE_DBMS for
> >the user. I believe a frequently asked question is "how do I make the
> >samples work with (MySQL|PostgreSQL|Oracle|DB2|Sybase|Access)?"
>
That's why I wouldn't give up too easily on making the db setup work
from a normal sql script. Currently we have the .sql out there, but
I'm not sure it's up to date (though it looks like it), and if it's
not used, it's certainly in danger of getting out of date at some
point.
But the .script fil
Excellent - I'll check it out tonight (which depending on where you live
is probably in the wee hours of the AM).
we'll see :)
Last night I noticed that the hsql block had the correct db.script, but
it wasn't getting copied into the webapp - I assume this is fixed by #2
above.
Ups.. I forgot
At 03:39 AM 3/12/2003, you wrote:
On 11.Mar.2003 -- 06:33 PM, Torsten Curdt wrote:
> But since this is only used for the "personal" datasource it doesn't
> make any sense all to have it configurable in the properties. It's just
> for the example database. Let's KISS :)
Well, the idea was to make i
At 06:24 AM 3/12/2003, you wrote:
Ok, team, I fixed the esql samples. Please try.
Changes:
1) Now the database block has the script and properties
file to fill the hsqldb with the sample entries.
I wasn't quite sure whether it should go into the hsqldb
block or into the databases
Ok, team, I fixed the esql samples. Please try.
Changes:
1) Now the database block has the script and properties
file to fill the hsqldb with the sample entries.
I wasn't quite sure whether it should go into the hsqldb
block or into the databases block. Maybe we should split
On 11.Mar.2003 -- 06:33 PM, Torsten Curdt wrote:
> >>I wanted to look after the esql samples but found
> >>
> >>1) the hsqldb not being filled (where did we do this before?)
> >
> >
> >I noticed this a few days ago, but haven't had time to writ
Geoff Howard wrote:
For now, though for purposes of reviving the samples quickly it may
be as easy as re-commiting a new db.script into the database block
with the changes in it.
IIUC hsql uses this file as its persistent store of data - when you
shut down, it gets overwritten with what is in
For now, though for purposes of reviving the samples quickly it may be as
easy as re-commiting a new db.script into the database block with the
changes in it.
IIUC hsql uses this file as its persistent store of data - when you shut
down, it gets overwritten with what is in memory. So, if you
Hm... I see. So it's enough to just copy the sql script into the
WEB-INF/db location. I'll take look...
I was just getting ready to see if there is an ant call to process a
sql script over jdbc (I'm sure there is, just don't know ant well
enough) but I'd make slow progress now as I'm very time li
At 12:33 PM 3/11/2003, you wrote:
I wanted to look after the esql samples but found
1) the hsqldb not being filled (where did we do this before?)
I noticed this a few days ago, but haven't had time to write about it.
I'm pretty sure from experiencing adding a new table to the demo a
I wanted to look after the esql samples but found
1) the hsqldb not being filled (where did we do this before?)
I noticed this a few days ago, but haven't had time to write about it.
I'm pretty sure from experiencing adding a new table to the demo a month
ago that the hsqldb was
At 11:15 AM 3/11/2003, you wrote:
I wanted to look after the esql samples but found
1) the hsqldb not being filled (where did we do this before?)
I noticed this a few days ago, but haven't had time to write about it. I'm
pretty sure from experiencing adding a new table to the demo a
I wanted to look after the esql samples but found
1) the hsqldb not being filled (where did we do this before?)
2) the jdbc url, user and password not being replaced
Did I miss something with the new build system?
Can anyone provide me a pointer so I can fix it?
Thanks
--
Torsten
smime.p7s
gzilla/show_bug.cgi?id=8062
[PATCH] ESQL Samples for the HSSF Serializer, and corrections to state tax table
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RE
gzilla/show_bug.cgi?id=8062
[PATCH] ESQL Samples for the HSSF Serializer, and corrections to state tax table
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RE
gzilla/show_bug.cgi?id=8062
[PATCH] ESQL Samples for the HSSF Serializer, and corrections to state tax table
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RE
gzilla/show_bug.cgi?id=8062
[PATCH] ESQL Samples for the HSSF Serializer, and corrections to state tax table
--- Additional Comments From [EMAIL PROTECTED] 2002-04-18 16:38 ---
Added a bug for the internationalization problems.
"
HSSF internazionalization problems with n
gzilla/show_bug.cgi?id=8062
[PATCH] ESQL Samples for the HSSF Serializer, and corrections to state tax table
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|AS
gzilla/show_bug.cgi?id=8062
[PATCH] ESQL Samples for the HSSF Serializer, and corrections to state tax table
--- Additional Comments From [EMAIL PROTECTED] 2002-04-18 13:52 ---
Sorry, I didn't post the full stacktrace.
In reality, if I serialize to xml it goes through ok, it'
gzilla/show_bug.cgi?id=8062
[PATCH] ESQL Samples for the HSSF Serializer, and corrections to state tax table
--- Additional Comments From [EMAIL PROTECTED] 2002-04-18 11:53 ---
Would that not indicate a bug in the TraxTransformer rather than in this patch?
(its not handling italian r
gzilla/show_bug.cgi?id=8062
[PATCH] ESQL Samples for the HSSF Serializer, and corrections to state tax table
[EMAIL PROTECTED] changed:
What|Removed |Added
Stat
gzilla/show_bug.cgi?id=8062
[PATCH] ESQL Samples for the HSSF Serializer, and corrections to state tax table
--- Additional Comments From [EMAIL PROTECTED] 2002-04-14 13:20 ---
Created an attachment (id=1552)
the actual example: src/webapp/samples/poi/content/dynamic/stateta
gzilla/show_bug.cgi?id=8062
[PATCH] ESQL Samples for the HSSF Serializer, and corrections to state tax table
--- Additional Comments From [EMAIL PROTECTED] 2002-04-14 13:19 ---
put stylesheet in src/webapp/samples/poi/style
gzilla/show_bug.cgi?id=8062
[PATCH] ESQL Samples for the HSSF Serializer, and corrections to state tax table
--- Additional Comments From [EMAIL PROTECTED] 2002-04-14 13:18 ---
Created an attachment (id=1551)
stylesheet for the esql e
gzilla/show_bug.cgi?id=8062
[PATCH] ESQL Samples for the HSSF Serializer, and corrections to state tax table
--- Additional Comments From [EMAIL PROTECTED] 2002-04-14 13:18 ---
Created an attachment (id=1550)
fixes database values, adds new esql sample to s
gzilla/show_bug.cgi?id=8062
[PATCH] ESQL Samples for the HSSF Serializer, and corrections to state tax table
Summary: [PATCH] ESQL Samples for the HSSF Serializer, and
corrections to state tax table
Product: Cocoon 2
Version: Current CVS
Pl
38 matches
Mail list logo
