Databases
StackOverflow2013
Postsdbo
POComputed columns sometimes missing from SELECT *
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POComputed columns sometimes missing from SELECT *
    primarykey
    data
    text
    <p>In SQL Azure, I have a table more or less set up like this, with two computed columns (<code>IsExpired</code> and <code>IsDeadlineExpired</code>) that simply compare non-nullable datetime columns to the current time:</p> <pre><code>CREATE TABLE [dbo].[Stuff] ( [StuffId] int NOT NULL IDENTITY(1,1), [Guid] uniqueidentifier NOT NULL, [ExpirationDate] datetime NOT NULL, [DeadlineDate] datetime NOT NULL, [UserId] int NOT NULL, [IsExpired] AS CAST((CASE WHEN [ExpirationDate] &lt; GETUTCDATE() THEN 1 ELSE 0 END) AS bit), [IsDeadlineExpired] AS CAST((CASE WHEN [DeadlineDate] &lt; GETUTCDATE() THEN 1 ELSE 0 END) AS bit), CONSTRAINT [PK_StuffId] PRIMARY KEY ([StuffId]), CONSTRAINT [UNQ_Guid] UNIQUE([Guid]), ) GO </code></pre> <p>I have a stored procedure with several result sets, one of which pulls:</p> <pre><code>SELECT * FROM [dbo].[Stuff] WHERE [Guid] = @guid </code></pre> <p>I've recently noticed error logs indicating that sometimes when the result set is read with <code>SqlDataReader</code>, <code>SqlDataReader.GetOrdinal("IsExpired")</code> fails with <code>IndexOutOfRangeException</code>. I know the preceding columns work fine even in those cases, since they're read in preceding lines of code with no errors. I also believe the result sets from the procedure are in proper sequence since they don't share column names (otherwise reading the earlier columns would similarly fail).</p> <p>Also: most of the time everything seems to work perfectly.</p> <p>Can this somehow be attributed to Azure transient faults?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMichael Berkowski
    1. USMike Asdf
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POComputed columns sometimes missing from SELECT *
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POComputed columns sometimes missing from SELECT *
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POComputed columns sometimes missing from SELECT *
      1. USknightpfhor
      1. VTFavorite
    1. COAnd yet another reason supporting my choice to never use `*`
      singulars
      1. POComputed columns sometimes missing from SELECT *
      1. USlc.
    2. COI agree, reworking it to select explicit columns would be preferable and would probably make it work 100%, but I never expected `*` to behave like this. I mainly posted it because it's such a noodle-scratcher.
      singulars
      1. POComputed columns sometimes missing from SELECT *
      1. USMike Asdf
    3. COYeah it is rather odd. Were those columns added after the fact?
      singulars
      1. POComputed columns sometimes missing from SELECT *
      1. USlc.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload