Hi

FAST have developed an extension to the PostgreSQL - replacing the storage
manager with a more enterprise enabled version. This extension throws some
errors that need SQLState codes.

Thus, we would like to ask a couple of question regarding SQLState codes.

1/ Is there a convention for creating sub-class codes. I.e., not major
classes, but children. do we have to take the next available number, or do
we increment in 100s?
2/ If there is no convention is it ok to use the letter 'x' for all our
State codes? eg. if we want to add a state under the "53" class, we would
use "53x001", "53x002" and so on.
2/ If we have some States that might become common to the code in future
releases, can we give them in as patches? Eg. we have an error "Archive log
is full" with SQLState 53x00. It might be possible that OSS code might want
to throw the same, if not similar, message. Can we give common errors such
as that in for patching? Would the community accept these patches?

We would appreciate having your inputon this matter.

Mahesh Swamy
Software Engineer
Fujitsu Australia Software Technology
Address: 14 Rodborough Road, Frenchs Forest NSW 2086
Tel: +61 2 9452 9000
Fax: +61 2 9975 2899
Email: [EMAIL PROTECTED]
Web site: www.fastware.com

This is an email from Fujitsu Australia Software Technology Pty Ltd, ABN 27 003 693 
481. It is confidential to the ordinary user of the email address to which it was 
addressed and may contain copyright and/or legally privileged information. No one else 
may read, print, store, copy or forward all or any of it or its attachments. If you 
receive this email in error, please return to sender. Thank you.

If you do not wish to receive commercial email messages from Fujitsu Australia 
Software Technology Pty Ltd, please email [EMAIL PROTECTED]



---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
      subscribe-nomail command to [EMAIL PROTECTED] so that your
      message can get through to the mailing list cleanly

Reply via email to