Re: default values

On Jun 29, 2006, at 2:12 PM, John Siracusa wrote:

> Should it be this?
>
>     INSERT INTO mytable (name) VALUES ('foo');
>
> Or should it be this?
>
>     INSERT INTO mytable (name, flag) VALUES ('foo', 1);
>
> They may seem identical, but now imagine if the default value in the
> "flag" column metadata was something other than 123.
>
> Anyone have any opinions about how this should be handled?

i think it should be the latter.  if its specified in ther perl  
metadata, that should take precedence as it might be an override.

example:
        create table insert_logger ( transaction_id serial primary key,  
logged_by interger references loggers(id) not null default 10 );
        loggers:
                id - name
                10 - 'not specified'
                11 - 'perl, rosedb'
                12 - 'perl, raw''
                13 - 'php'
                14 - 'python'

then , depending on the app, you'd want a default value as specified.
perhaps thats more of a config implementation than a metadata


| - - - - - - - - - - - - - - - - - - - -
| RoadSound.com / Indie-Rock.net
| Collaborative Online Management And Syndication Tools
| - - - - - - - - - - - - - - - - - - - -





Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642