#1  
Old 8th December 2006, 09:01 PM
Ole Willy Tuv
 
Posts: n/a
Default Column default option EMPTY

The proprietary column default option EMPTY is pretty much obsolete and
should IMO be removed.

The only place EMPTY has a meaning is in character string columns, meaning
that the default value is an empty string, as opposed to NULL. The
official/standard way of specifying an empty string is ''.

Currently the SQL engine allows EMPTY to be specificed as the default value
for all column types, which is meaningless.

Ole


  #2  
Old 9th December 2006, 12:13 AM
Eivind Bakkestuen [NDD]
 
Posts: n/a
Default Re: Column default option EMPTY

> The proprietary column default option EMPTY is pretty much obsolete
> and should IMO be removed.


I dont think we'll do that, as long as the proprietary extension is
meaningful to the engine (it translates directly to a core default
descriptor type).

--

Eivind Bakkestuen
Nexus Database Systems Pty Ltd


  #3  
Old 11th December 2006, 02:41 AM
Thorsten Engler
 
Posts: n/a
Default Re: Column default option EMPTY

Ole Willy Tuv wrote:

> What does an "empty" integer value look like,

0

> or an empty datetime

31/12/1899 (= TDateTime 0)

> value, or an empty boolean value ?

False

Cheers,
Thorsten
  #4  
Old 11th December 2006, 03:00 AM
Ole Willy Tuv
 
Posts: n/a
Default Re: Column default option EMPTY

Eivind,

>> The proprietary column default option EMPTY is pretty much obsolete
>> and should IMO be removed.

>
> I dont think we'll do that, as long as the proprietary extension is
> meaningful to the engine (it translates directly to a core default
> descriptor type).


Yes, but the descriptor is meaningless for anything but character string
columns.

What does an "empty" integer value look like, or an empty datetime value, or
an empty boolean value ?

If you choose to keep this descriptor type, you should probably restrict its
use to character string columns.

Ole


  #5  
Old 11th December 2006, 04:31 AM
Thorsten Engler
 
Posts: n/a
Default Re: Column default option EMPTY

Ole Willy Tuv wrote:
> > > What does an "empty" integer value look like,

> > 0

> That's a bit artifical. 0 is a normal value.

It's not "artificial" It is what you get if you have an integer field
that's NULL and use the AsInteger property.


> > > or an empty datetime

> > 31/12/1899 (= TDateTime 0)

> Silly IMO.

It's not silly. It's what you get if you have a datetime field that's
NULL and use the AsDateTime property.


> > > value, or an empty boolean value ?

> > False

> Again a normal value.


And once again. It's what you get if you have a TBooleanField that's
NULL and use the AsBoolean property.


> IMO, the value that makes sense for an "Empty" descriptor is an empty
> string (length 0).

Let's agree to disagree.

Cheers,
Thorsten
  #6  
Old 11th December 2006, 05:00 AM
Ole Willy Tuv
 
Posts: n/a
Default Re: Column default option EMPTY

Thorsten,

>> What does an "empty" integer value look like,

> 0


That's a bit artifical. 0 is a normal value.

>> or an empty datetime

> 31/12/1899 (= TDateTime 0)


Silly IMO.

>> value, or an empty boolean value ?

> False


Again a normal value.

IMO, the value that makes sense for an "Empty" descriptor is an empty string
(length 0).

Ole


  #7  
Old 11th December 2006, 05:30 AM
Ole Willy Tuv
 
Posts: n/a
Default Re: Column default option EMPTY

Thorsten,

> Let's agree to disagree.


Sure, no problem.

Ole


  #8  
Old 11th December 2006, 11:08 AM
Shane Stump
 
Posts: n/a
Default Re: Column default option EMPTY

Thorsten Engler wrote:
> Ole Willy Tuv wrote:
>>>> What does an "empty" integer value look like,
>>> 0

>> That's a bit artifical. 0 is a normal value.

> It's not "artificial" It is what you get if you have an integer field
> that's NULL and use the AsInteger property.
>
>
>>>> or an empty datetime
>>> 31/12/1899 (= TDateTime 0)

>> Silly IMO.

> It's not silly. It's what you get if you have a datetime field that's
> NULL and use the AsDateTime property.
>
>
>>>> value, or an empty boolean value ?
>>> False

>> Again a normal value.

>
> And once again. It's what you get if you have a TBooleanField that's
> NULL and use the AsBoolean property.
>
>
>> IMO, the value that makes sense for an "Empty" descriptor is an empty
>> string (length 0).

> Let's agree to disagree.
>
> Cheers,
> Thorsten


Thorsten,

Why is EMPTY defaulting to DELPHI values <BG> <BG>!!!

Merry XMAS!

Shane
  #9  
Old 11th December 2006, 12:39 PM
Ole Willy Tuv
 
Posts: n/a
Default Re: Column default option EMPTY

Shane,

<< Why is EMPTY defaulting to DELPHI values <BG> <BG>!!! >>

One of the design goals must have been to make NexusDB look as esoteric as
possible

Ole


  #10  
Old 11th December 2006, 03:37 PM
Shane Stump
 
Posts: n/a
Default Re: Column default option EMPTY

Ole Willy Tuv wrote:
> Shane,
>
> << Why is EMPTY defaulting to DELPHI values <BG> <BG>!!! >>
>
> One of the design goals must have been to make NexusDB look as esoteric as
> possible
>
> Ole
>
>

I would AGREE with you on that! I do wish Borland had used more
conventional NULLs for data values (but I got use to them (initially it
required several Spaten Optimators))!

Merry XMAS!

Shane


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Non-installer download option for new versions. Hannes Danzl[NDD] nexusdb.public.support.portal 6 2nd September 2009 08:41 AM
Metadata issue, default column value Ole Willy Tuv nexusdb.public.support.sql 14 14th December 2006 12:59 PM
Returning an empty dataset Hans Hasenack nexusdb.public.support.sql 7 12th September 2006 05:26 PM
Search Option & DateTime Fields IN Report Builder 10 RAP Barry Noble nexusdb.public.support.thirdparty 0 21st July 2006 12:30 AM
Result Fields are empty Bernhard Roos nexusdb.public.support.sql 6 3rd December 2005 04:31 AM


All times are GMT +11. The time now is 09:12 AM.


Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.