db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Monroe" <Greg.Mon...@DukeCE.com>
Subject Some stuff for 3.3-RC1 or not?
Date Tue, 21 Nov 2006 02:56:37 GMT
I've got some finished stuff and some stuff on the 
almost done list that may or may not be wanted in RC1.
I know we're down to the wire on this, and wanted to 
see what folks thought about adding these to RC1 or 
doing it later (RC2?).
 
Here's the list and status:
 
Done:
 
Changes to the Derby DB generator adaptor to make it
work with the test-project / add support for sized
Binary/Varbinary types, plus some type mapping 
tweaks the test-project showed as not working.
 
Done:
 
Changes to the test-schema.xml to make it more cross
DB friendly, e.g. some test tables use non-numeric
primary keys and some DB adaptors (especially Derby) 
may fail to generate clean SQL if the idMethod not 
specifically set to "none" on them.
 
Done - but not tested:
 
In adding non-default values for all the package and
prefix/suffix settings to the test-project, I found 
a couple of template bugs (and some test-schema 
tweaks).  As the templates are now, you can't 
define an object or peer subpackage and generate
good code.  I've got templates that compile but
can't test until I've updated the Test-program code
to use the new subpackages.
 
Partially done:
 
Modifying the test project to use the sub-packages.
This isn't hard, 
 
Started and could possibly be done:
 
A first pass at an ant script to test against them 
most common combinations... that may find more
issues to work on.
 
FYI - I'm just lounging about the house this week, 
(US Thanksgiving) so I can dedicate some time to 
knocking this out without a lot of interference. But
if RC1's locked down, then... 
 

Duke CE Privacy Statement
Please be advised that this e-mail and any files transmitted with it are confidential communication
or may otherwise be privileged or confidential and are intended solely for the individual
or entity to whom they are addressed.  If you are not the intended recipient you may not rely
on the contents of this email or any attachments, and we ask that you  please not read, copy
or retransmit this communication, but reply to the sender and destroy the email, its contents,
and all copies thereof immediately.  Any unauthorized dissemination, distribution or copying
of this communication is strictly prohibited.



Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message