Talk:Check constraint
Added links to this page from:
 | This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||
| ||||||||
Remark
Added links to this page from:
http://en.wikipedia.org/wiki/Update_%28SQL%29
http://en.wikipedia.org/wiki/Insert_%28SQL%29
http://en.wikipedia.org/wiki/SQL-92
http://en.wikipedia.org/wiki/Virtuoso_Universal_Server
This article currently has the following examples
- Some examples of dangerous constraints include:
- CHECK ((select count(*) from invoices where invoices.customerId = customerId) < 1000)
- CHECK (dateInserted = CURRENT_DATE)
- CHECK (countItems = RAND())
What is "dangerous" with these check constraints? --Abdull (talk) 15:34, 26 September 2012 (UTC)
UNKNOWN?
Why does this article refer to UNKNOWN? In SQL 'unknown' is represented by NULL, so surely this should say NULL? 80.41.77.9 (talk) 11:13, 16 August 2021 (UTC)
Content Disclaimer
Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.
- The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
- There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
- It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
- Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
- Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.