COMMENT statement

[Veaceslav Chicu <cs...@infologic.fr>]

Hi,

I haven't found COMMENT statement
it's not present in Derby? or it's me?

if it's not present, can we add it?

thank you,
Slavic

Re: COMMENT statement

[Veaceslav Chicu <cs...@infologic.fr>]

if you don't need, nobody needs :)

you don't know me to say what I need :)
you are like Stalin, where are you from, which country?

why derby has SYSTABLES? for what? can you say? why can I access SYSTABLES?
it's a security hole, do not show schema to any user, use files with 
proprietary format,
why you use CATALOG/METADATA in a relational database? why should I 
create a parallel structure?

if derby has SYSTABLES why it's not complete?

who is adding TODOs ? can I add todo's or wishes for derby?

Slavic
P.S. I think about CATALOG/METADA as a description of database, that 
help me know what is there, if I'm wrong please correct me, show me the 
good way


Jan Hlavaty wrote:

>Veaceslav Chicu wrote:
>  
>
>>I use that for schema documentation, my memory is not so good
>>I have a widget, with F1, app user can see comment for the field
>>    
>>
>
>You don't need support for COMMENT ON for that feature - you can do that
>yourself with a help table.
>
>Jan
>  
>

Re: COMMENT statement

[Jan Hlavaty <hl...@code.cz>]

Veaceslav Chicu wrote:
> 
> I use that for schema documentation, my memory is not so good
> I have a widget, with F1, app user can see comment for the field

You don't need support for COMMENT ON for that feature - you can do that
yourself with a help table.

Jan

Re: COMMENT statement

[Veaceslav Chicu <cs...@infologic.fr>]

Hi,

I use that for schema documentation, my memory is not so good
I have a widget, with F1, app user can see comment for the field

my database is opened for the user, why should I hide my schema? I have 
grants for the rights (not in derby ?)
or I should create databases without any comment on field, maybe field 
name is something like "87da98aa" ???

if you want to hide your schema encode database, rename fields, do not 
use COMMENT ON, I want to give to the user possibility to work with 
data, to comment fields, to see my comments, I found that COMMENT ON is 
good for that, it's more natural, for a desktop application

what you are doing with derby? why you are so paranoic? maybe it's not 
for you, maybe you should use a specialised product with a better security

best regards,
Slavic
P.S. if a hacker broke into your database using SQL injection, your 
application have a security hole, or database server has a security hole




Jan Hlavaty wrote:

> On the contrary, I think we don't need this ;-)
>
> The fact that some other database has a feature does not imply we must 
> have it too. Adding a feature should be justified.
>
> Think of it this way - what is it good for? Who and how would use it?
>
> Comments on schema objects are good for someone that:
> 1) can get into the schema in the first place, so is DBA or 
> interactive SQL user with direct access to database
> 2) does not know the schema well enough
> 3) cannot get regular documentation about the schema
>
> Who is the guy that meets all these requirements? A hacker who broke 
> into your database using SQL injection ;-)
>
> Just my 2c.
>
> Jan
>
>
> Marshall Dunbar wrote:
>
>> I agree.  Comment On would be a very useful feature.  Does anyone know
>> the process to get this on the development "to-do" list?
>>
>> Marshall
>>
>>
>> On Tue, 14 Sep 2004 09:06:24 +0300, Veaceslav Chicu <cs...@infologic.fr> 
>> wrote:
>>
>>> yes, exactly
>>> it's present in other databases also, not db2 only
>>>
>>> COMMENT ON
>>> https://aurora.vcu.edu/db2help/db2s0/frame3.htm#sqls0609
>>>
>>> I'd like Derby more, with that
>>>
>>> best regards,
>>> Slavic
>>
>
>

Re: COMMENT statement

[Jan Hlavaty <hl...@code.cz>]

On the contrary, I think we don't need this ;-)

The fact that some other database has a feature does not imply we must 
have it too. Adding a feature should be justified.

Think of it this way - what is it good for? Who and how would use it?

Comments on schema objects are good for someone that:
1) can get into the schema in the first place, so is DBA or interactive 
SQL user with direct access to database
2) does not know the schema well enough
3) cannot get regular documentation about the schema

Who is the guy that meets all these requirements? A hacker who broke 
into your database using SQL injection ;-)

Just my 2c.

Jan


Marshall Dunbar wrote:
> I agree.  Comment On would be a very useful feature.  Does anyone know
> the process to get this on the development "to-do" list?
> 
> Marshall
> 
> 
> On Tue, 14 Sep 2004 09:06:24 +0300, Veaceslav Chicu <cs...@infologic.fr> wrote:
> 
>>yes, exactly
>>it's present in other databases also, not db2 only
>>
>>COMMENT ON
>>https://aurora.vcu.edu/db2help/db2s0/frame3.htm#sqls0609
>>
>>I'd like Derby more, with that
>>
>>best regards,
>>Slavic

Re: COMMENT statement

[Daniel John Debrunner <dj...@debrunners.com>]

Marshall Dunbar wrote:

> I agree.  Comment On would be a very useful feature.  Does anyone know
> the process to get this on the development "to-do" list?

Any feature that is discussed on the mailing lists can be seen as part
of the overall 'to-do' list. The to-do list is not a formal list of
items that will be added to Derby, just the set of items that could be
added to Derby. Anything on that list will only get implemented if
someone is interested in working on it. That someone can be a committer,
a contributor, or a developer who has never touched Derby before (and
thus becomes a contributor).

The to-do list page (http://incubator.apache.org/derby/DerbyToDo.html)
is intended to provide a quick view of the possible items, I can (or
others can) update it from time to time based upon discussions in the
maling lists. Jira (bug & feature tracking) could also be used to
capture requests.

Note that Derby is following the Apache DB guidelines which talks about
new features in the Changes section of http://db.apache.org/source.html
and that contributors should have a CLA on file (see discussion on
derby-dev).

It is also useful to read the Derby charter and proposal
(http://incubator.apache.org/derby/derby_proposal.html)
which is what our sponsor (Apache DB project) voted on to accept Derby
into incubation.

Dan.

Re: COMMENT statement

[Marshall Dunbar <ma...@gmail.com>]

I agree.  Comment On would be a very useful feature.  Does anyone know
the process to get this on the development "to-do" list?

Marshall


On Tue, 14 Sep 2004 09:06:24 +0300, Veaceslav Chicu <cs...@infologic.fr> wrote:
> yes, exactly
> it's present in other databases also, not db2 only
> 
> COMMENT ON
> https://aurora.vcu.edu/db2help/db2s0/frame3.htm#sqls0609
> 
> I'd like Derby more, with that
> 
> best regards,
> Slavic

Re: COMMENT statement

[Veaceslav Chicu <cs...@infologic.fr>]

yes, exactly
it's present in other databases also, not db2 only

COMMENT ON
https://aurora.vcu.edu/db2help/db2s0/frame3.htm#sqls0609

I'd like Derby more, with that

best regards,
Slavic

Satheesh Bandaram wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> May be I spoke too fast... Were you refering to COMMENT statement that
> DB2 has? If so, Derby doesn't have that. It would be a good addition
> to Derby.
>
> Satheesh
>
> Satheesh Bandaram wrote:
>
> | Isn't this what you are looking for?
> |
> | ~    Two dashes (--) and a newline character delimit a comment, as
> | per ~    the SQL-92 standard. The two dashes start the comment and
> | the ~    newline character ends the comment.
> |
> |
> | I got that from the *Capitalization and Special Characters* section
> | in the Reference manual.
> |
> | Satheesh
> |
> | Veaceslav Chicu wrote:
> |
> | | Hi, | | I haven't found COMMENT statement it's not present in
> | Derby? or | it's me? | | if it's not present, can we add it? | |
> | thank you, Slavic | |
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFBRkjJENVNIY6DZ7ERAjdmAJ0YJhprtxxjDQPWn7O78J3SDB6eLgCghu/f
> o+9nOuhSRTZqVrp4U5QtyvQ=
> =imaF
> -----END PGP SIGNATURE-----
>
>

Re: COMMENT statement

[Satheesh Bandaram <sa...@Sourcery.Org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
May be I spoke too fast... Were you refering to COMMENT statement that
DB2 has? If so, Derby doesn't have that. It would be a good addition
to Derby.

Satheesh

Satheesh Bandaram wrote:

| Isn't this what you are looking for?
|
| ~    Two dashes (--) and a newline character delimit a comment, as
| per ~    the SQL-92 standard. The two dashes start the comment and
| the ~    newline character ends the comment.
|
|
| I got that from the *Capitalization and Special Characters* section
| in the Reference manual.
|
| Satheesh
|
| Veaceslav Chicu wrote:
|
| | Hi, | | I haven't found COMMENT statement it's not present in
| Derby? or | it's me? | | if it's not present, can we add it? | |
| thank you, Slavic | |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
 
iD8DBQFBRkjJENVNIY6DZ7ERAjdmAJ0YJhprtxxjDQPWn7O78J3SDB6eLgCghu/f
o+9nOuhSRTZqVrp4U5QtyvQ=
=imaF
-----END PGP SIGNATURE-----

Re: COMMENT statement

[Satheesh Bandaram <sa...@Sourcery.Org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
Isn't this what you are looking for?

~    Two dashes (--) and a newline character delimit a comment, as per
~    the SQL-92 standard. The two dashes start the comment and the
~    newline character ends the comment.


I got that from the *Capitalization and Special Characters* section in
the Reference manual.

Satheesh

Veaceslav Chicu wrote:

| Hi,
|
| I haven't found COMMENT statement it's not present in Derby? or
| it's me?
|
| if it's not present, can we add it?
|
| thank you, Slavic
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
 
iD8DBQFBRjceENVNIY6DZ7ERAmVFAKCqrB+HcthIXst5ZaSrmeFUrcG51wCeN1sc
fO/LqOZyrOg6uksPi2QhGqg=
=rEn4
-----END PGP SIGNATURE-----