Joe Celko introduces more powerful scales such as Interval, Log interval and ratio scales; before moving on to conversions, punctuation and units. Finally he gives guidelines as to how best to use scales in a database.
2011-07-27
4,781 reads
It is certainly possible to fake an Array in SQL, but there are only a few occasions when it would be the best design. Most often, the wish for an array in SQL is a sign of a forlorn struggle against poorly-normalised data. One of the worst sins against Codd is the repeating group, as Joe Celko explains.
2011-07-20
3,438 reads
Joe Celko discusses Nominal, Categorical, Absolute, Ordinal and Rank scales. These are the weakest scales we can use, starting with the weakest.
2011-07-06
6,755 reads
Character-handling in SQL is not particularly straightforward, and confusion about collation and character encoding is a common cause of problems with searching, joining, and sorting.
2011-06-01
9,603 reads
A confusion about the nature of numbers can lead to a number of problems in database applications. Joe Celko gives a simple guide to the subject
2011-05-18
12,452 reads
It is dangerous to assume that your data is sound. SQL already has intrinsic ways to cope with missing, or unknown data in its comparison predicate operators, or Theta operators. Can SQL be more effective in the way it deals with data quality? Joe Celko describes how the SQL Standard could soon evolve to deal with data in ways that allow aggregation and windowing in cases where the data quality is less than perfect.
2011-04-01
6,632 reads
You can easily re-factor bad DML code, but if a database design is wrong, you can do little to rescue the problem, even with expert queries. So what constitutes 'wrong RDBMS design? What are these errors that continually crop up? How can you recognise them and fix them? Joe embarks on a new series of articles by identifying a series of bad practices based on the habit of 'splitting' that which shouldn't be split.
2010-09-08
2,767 reads
What can we use in SQL instead of E. F. Codd's T theta operators for best-fit? Joe Celko returns with another puzzle that isn't new, in fact it already features “Swedish”, “Croatian” and “Colombian” solutions in chapter 17 of Joe's 'SQL for Smarties' book. These were all written before CTEs or the new WINDOW functions. Is there now a better solution? Was there one even then? We leave it to the readers to provide the answer!
2010-01-25
1,738 reads
Joe Celko comes back with a puzzle that isn't new, but one where the answer he originally gave now seems archaic: It is a deceptively simple problem, but is it true that the new features of SQL have simplified the solution? We leave it to the readers to provide the answer!
2009-09-28
3,571 reads
Our first Stumper sees Joe Celko providing a conundrum with a prize for anyone who can come up with a better solution than he can.
2009-07-27
3,291 reads
By James Serra
(This is the third post in a three-part series on how AI is changing...
Continuing with my takeaways from SQLCon and FabCon Europe in Barcelona, let’s talk about...
By Steve Jones
Next year the PASS Data Community Summit is in DENVER! and London, but Denver...
Comments posted to this topic are about the item Pay for Performance, which is...
Comments posted to this topic are about the item Helping an English Student with...
Comments posted to this topic are about the item Adding Bits I
I have a table, dbo.bittest, where I am testing an application response. This has this structure:
CREATE TABLE [dbo].[BitTest] ( [insertdate] [datetime] NULL CONSTRAINT [DF__BitTest__insertd__300F11AC] DEFAULT (getdate()), [a] [bit] NULL ) ON [PRIMARY] GOMy application runs this code:
INSERT dbo.BitTest
(
insertdate,
a
)
VALUES
(DEFAULT, 'true')
GO
See possible answers