Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 5 of 5 total
Thread Primary key with non required fields
Mon, Oct 30 2017 4:26 PMPermanent Link

Jose Eduardo Helminsky

HPro Informatica

Tim

As a DBISAM user at least I will try to ask you if could be possible to define a property in ElevateDB that does not demand required fields in the compound indexes in PK. In my new projects started with ElevateDB they are all required but I have some applications built with DBISAM that have compound indexes with fields non required in primary key.

Thanks in advance
Tue, Oct 31 2017 3:28 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Jose


From memory, and because I asked for it as well, I think you will find the answer is no. Its part of the sql spec.

Roy Lambert
Tue, Oct 31 2017 5:26 AMPermanent Link

Jose Eduardo Helminsky

HPro Informatica

Roy Lambert wrote:

<<
From memory, and because I asked for it as well, I think you will find the answer is no. Its part of the sql spec.
>>

I understand the point and agree with following SQL specs but I am still in DBISAM and it is very hard to migrate data and source code in these situations. Of course Tim has his reasons to do or not do this (I donīt know how hard it is) but in my opinion it will help DBISAM users to convert the applications easily.

Note that I am just asking for a property to change the default behaviour of ElevateDB.

But, letīs wait Timīs answer and his point of view.
Tue, Oct 31 2017 6:20 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Jose


>But, letīs wait Timīs answer and his point of view.

If he builds it in now I (and I suspect a few others) will jump up and down and scream whilst holding our breaths until we turn blue Smiley

Roy
Fri, Nov 3 2017 12:56 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Eduardo,

<< As a DBISAM user at least I will try to ask you if could be possible to define a property in ElevateDB that does not demand required fields in the compound indexes in PK. In my new projects started with ElevateDB they are all required but I have some applications built with DBISAM that have compound indexes with fields non required in primary key.  >>

What you want is a unique key, not a primary key.  Unique keys allow for NULLs, but otherwise can be used just like primary keys with foreign-key relationships, etc.

Likewise, when you perform the migration of a DBISAM database, you can set the ConvertPrimaryToUnique parameter to True to automatically convert your primary indexes in DBISAM to unique keys in EDB.

Tim Young
Elevate Software
www.elevatesoft.com
Image