Opened 12 years ago
Closed 7 years ago
#840 closed defect (fixed)
Insert feature fails on table with computed column
Reported by: | gBecker | Owned by: | danstoica |
---|---|---|---|
Priority: | major | Milestone: | 3.7.0 |
Component: | SQLServer Spatial | Version: | 3.6.0 |
Severity: | 3 | Keywords: | |
Cc: | External ID: |
Description
When trying to insert a feature into a table with a computed column the insertion fails because this column/property must have been "NOT NULL".
I also tried to set a dummy value for this column but this fails, too, because computed columns couldn't be set.
So, my conclusion is that this must be a failure. I would have supposed that the property for the computed column must be marked as ReadOnly, but it wasn't. ReadOnly attribute was set to "false".
Change History (2)
comment:1 by , 12 years ago
comment:2 by , 7 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Considering this fixed due to fix for #920
Note:
See TracTickets
for help on using tickets.
Here is the script for creating the table:
CREATE TABLE [dbo].[Erschliessungen](
(
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY]