You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-user@db.apache.org by Nathan Smith <na...@labpro2000.com> on 2004/08/20 02:07:58 UTC
Official implementation request.
Hi all,
LabPro 2000 Ltd is a specialist provider of information management
systems including LIMS (Laboratory Information Management Systems). We
here at www.labpro2000.com currently use OJB as part of our eQual
application development (http://demo.labpro2000.com). This is a
redevelopment of the current application Labpro. To put it simply
LabPro, is a QA solution for any testing.
We use an RDBMS developed by a little known company called Progress
(http://www.progress.com/progress/index.ssp). The RDBMS is a very good
database but not many people have heard of it, so it is not really
mainstream.
The problem is this RDBMS allows records to be inserted with blank or
null values for fields of the primary key. For example we have a table
that uses 7 fields/columns as part of the PK. A record could be inserted
with 6 of those fields blank or null. The use of the table is a special
case as it defines range limits that testing results must fall within
for a particular product to be assigined a quality code. One of the
records in this table depending on what fields are blank can used for
multiple products. We also have another table which is used in similar
fashion
The proposal:
Can the repository.xml contain some property or database specific
metadata element which can be used to determine whether NULL's or blanks
can be used as ligitimate values for PK fields. Or maybe another way
would be to enable some sort of callback that can be implemented through
the Platform interface.
Look forward to hearing your ideas.
Nathan Smith
Software Developer
LabPro 2000 Limited
Phone: +64 4 586 6840
Facsimile: +64 4 586 6841
<ma...@labpro2000.com> nathan@labpro2000.com
<http://www.labpro2000.com/> www.labpro2000.com
Level 6, Riverside Tower on Daly, 15 Daly Street
Lower Hutt, New Zealand
Re: Official implementation request.
Posted by "Robert r. Sanders" <ro...@ipov.net>.
I'd tend to force an artificial primary key (as an
extra field); but I suppose the customization options offered by OJB
would allow you to write your own call-back to enable the kind of
functionality your talking about.
Clóvis Wichoski wrote:
> Hi,
>
> When we need this, I never use database NULL value for PK, instead I
> use a String initiated with 'NULL' then the Querys can change
>
> from:
>
> SELECT * FROM table1 WHERE field1 IS NULL AND field2 = '0001'
>
> to:
>
> SELECT * FROM table1WHERE field1 = 'NULL' AND field2 = '0001'
>
> This idea work on any Database, only you must to do is define what is
> your constant to NULL value.
>
> Hope this help
>
> Clóvis
>
> Nathan Smith wrote:
>
>> Hi all,
>>
>> LabPro 2000 Ltd is a specialist provider of information management
>> systems including LIMS (Laboratory Information Management Systems). We
>> here at www.labpro2000.com currently use OJB as part of our eQual
>> application development (http://demo.labpro2000.com). This is a
>> redevelopment of the current application Labpro. To put it simply
>> LabPro, is a QA solution for any testing.
>> We use an RDBMS developed by a little known company called Progress
>> (http://www.progress.com/progress/index.ssp). The RDBMS is a very good
>> database but not many people have heard of it, so it is not really
>> mainstream.
>>
>> The problem is this RDBMS allows records to be inserted with blank or
>> null values for fields of the primary key. For example we have a table
>> that uses 7 fields/columns as part of the PK. A record could be inserted
>> with 6 of those fields blank or null. The use of the table is a special
>> case as it defines range limits that testing results must fall within
>> for a particular product to be assigined a quality code. One of the
>> records in this table depending on what fields are blank can used for
>> multiple products. We also have another table which is used in similar
>> fashion
>>
>> The proposal:
>> Can the repository.xml contain some property or database specific
>> metadata element which can be used to determine whether NULL's or blanks
>> can be used as ligitimate values for PK fields. Or maybe another way
>> would be to enable some sort of callback that can be implemented through
>> the Platform interface.
>>
>> Look forward to hearing your ideas.
>>
>>
>> Nathan Smith
>>
>> Software Developer
>> LabPro 2000 Limited
>> Phone: +64 4 586 6840
>> Facsimile: +64 4 586 6841
>> <ma...@labpro2000.com> nathan@labpro2000.com
>> <http://www.labpro2000.com/> www.labpro2000.com
>>
>> Level 6, Riverside Tower on Daly, 15 Daly Street
>> Lower Hutt, New Zealand
>>
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-user-help@db.apache.org
>
--
Robert r. Sanders
Chief Technologist
iPOV
www.ipov.net
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org
RE: Official implementation request.
Posted by Nathan Smith <na...@labpro2000.com>.
Thanks for your response Clovis.
Our application will have to refactored/redeveloped to run against an
Oracle database some time in the future. This will mean massaging the
current data contained in the Progress database into the Oracle one. We
will most likely have to use the exact approach you have outlined. It
sounds like a good one to me. Most of the time it will mean a change of
looking up a record using WHERE field1 = '' to WHERE field1 = 'NULL'.
Not too much of a major, hopefully.
Nathan.
-----Original Message-----
From: Clóvis Wichoski [mailto:clovis_wichoski@uol.com.br]
Sent: Saturday, 21 August 2004 12:04 a.m.
To: OJB Users List
Subject: Re: Official implementation request.
Hi,
When we need this, I never use database NULL value for PK, instead I use
a String initiated with 'NULL' then the Querys can change
from:
SELECT * FROM table1 WHERE field1 IS NULL AND field2 = '0001'
to:
SELECT * FROM table1WHERE field1 = 'NULL' AND field2 = '0001'
This idea work on any Database, only you must to do is define what is
your constant to NULL value.
Hope this help
Clóvis
Nathan Smith wrote:
>Hi all,
>
>LabPro 2000 Ltd is a specialist provider of information management
>systems including LIMS (Laboratory Information Management Systems). We
>here at www.labpro2000.com currently use OJB as part of our eQual
>application development (http://demo.labpro2000.com). This is a
>redevelopment of the current application Labpro. To put it simply
>LabPro, is a QA solution for any testing.
>
>We use an RDBMS developed by a little known company called Progress
>(http://www.progress.com/progress/index.ssp). The RDBMS is a very good
>database but not many people have heard of it, so it is not really
>mainstream.
>
>The problem is this RDBMS allows records to be inserted with blank or
>null values for fields of the primary key. For example we have a table
>that uses 7 fields/columns as part of the PK. A record could be
>inserted with 6 of those fields blank or null. The use of the table is
>a special case as it defines range limits that testing results must
>fall within for a particular product to be assigined a quality code.
>One of the records in this table depending on what fields are blank can
>used for multiple products. We also have another table which is used in
>similar fashion
>
>The proposal:
>Can the repository.xml contain some property or database specific
>metadata element which can be used to determine whether NULL's or
>blanks can be used as ligitimate values for PK fields. Or maybe another
>way would be to enable some sort of callback that can be implemented
>through the Platform interface.
>
>Look forward to hearing your ideas.
>
>
>Nathan Smith
>
>Software Developer
>LabPro 2000 Limited
>Phone: +64 4 586 6840
>Facsimile: +64 4 586 6841
> <ma...@labpro2000.com> nathan@labpro2000.com
><http://www.labpro2000.com/> www.labpro2000.com
>
>Level 6, Riverside Tower on Daly, 15 Daly Street
>Lower Hutt, New Zealand
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org
Re: Official implementation request.
Posted by Clóvis Wichoski <cl...@uol.com.br>.
Hi,
When we need this, I never use database NULL value for PK, instead I use
a String initiated with 'NULL' then the Querys can change
from:
SELECT * FROM table1 WHERE field1 IS NULL AND field2 = '0001'
to:
SELECT * FROM table1WHERE field1 = 'NULL' AND field2 = '0001'
This idea work on any Database, only you must to do is define what is
your constant to NULL value.
Hope this help
Clóvis
Nathan Smith wrote:
>Hi all,
>
>LabPro 2000 Ltd is a specialist provider of information management
>systems including LIMS (Laboratory Information Management Systems). We
>here at www.labpro2000.com currently use OJB as part of our eQual
>application development (http://demo.labpro2000.com). This is a
>redevelopment of the current application Labpro. To put it simply
>LabPro, is a QA solution for any testing.
>
>We use an RDBMS developed by a little known company called Progress
>(http://www.progress.com/progress/index.ssp). The RDBMS is a very good
>database but not many people have heard of it, so it is not really
>mainstream.
>
>The problem is this RDBMS allows records to be inserted with blank or
>null values for fields of the primary key. For example we have a table
>that uses 7 fields/columns as part of the PK. A record could be inserted
>with 6 of those fields blank or null. The use of the table is a special
>case as it defines range limits that testing results must fall within
>for a particular product to be assigined a quality code. One of the
>records in this table depending on what fields are blank can used for
>multiple products. We also have another table which is used in similar
>fashion
>
>The proposal:
>Can the repository.xml contain some property or database specific
>metadata element which can be used to determine whether NULL's or blanks
>can be used as ligitimate values for PK fields. Or maybe another way
>would be to enable some sort of callback that can be implemented through
>the Platform interface.
>
>Look forward to hearing your ideas.
>
>
>Nathan Smith
>
>Software Developer
>LabPro 2000 Limited
>Phone: +64 4 586 6840
>Facsimile: +64 4 586 6841
> <ma...@labpro2000.com> nathan@labpro2000.com
> <http://www.labpro2000.com/> www.labpro2000.com
>
>Level 6, Riverside Tower on Daly, 15 Daly Street
>Lower Hutt, New Zealand
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org