Thomas,

I'm finally finding time outside of class to actually formalize the
work I've done toward H2. For the record, I currently have working
code for the following features:

-Adding multiple columns at a time (ALTER TABLE test ADD col1 int ADD
col2 int ...)
-Adding columns to tables with views defined
-For SEQUENCES, now supporting MIN and MAX values as well as the CYCLE
option
-The === comparator

I'm just starting to do formal testing and creating patches, and I've
got a few questions saved up:

1) I currently have all of my changes in different sets of code (in
other words, I'd be submitting a different patch for each of the above
changes). Does it make more sense to combine all my changes into one
patch instead? (It seems like it wouldn't, but I want to be sure).

2) When I run TestAll.java from Eclipse, the program freezes
indefinitely on TestOutOfMemory.java. This happens when I run it on
the code checked out from SVN or on code with my changes. Any idea
what's happening? (I'm running a Ubuntu Linux operating system,
perhaps the Linux JVM handles memory differently than the test is
expecting) Commenting out the line to run TestOutOfMemory.java lets
the test proceed just fine.

3) Similarly, when I run "./build.sh test", it freezes indefinitely.

4) Running "./build.sh spellcheck" produces the following error:

Exception in thread "main" java.lang.Error: java.io.IOException:
Unsupported suffix: project for file: /h2database/h2/src/.project

I realize it's an Eclispe .project file that the script is balking on.
What should I do to circumvent the problem? (Similar problems occur
when running "./build.sh docs")
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/h2-database?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to