This question already has answers here:
Entity Framework - default values doesn't set in sql server table
(4 answers)
Closed 8 years ago.
I have a table with a uniqueidentifier column.
What is the Default Value or Binding i should set in order for each new row to generate a new uniqueidentifier?
Setting the default to newid() always returns 00000000-0000-0000-0000-000000000000
EDIT:
Apparently i got it all wrong, the insert was done from Entity Framework, and it doesn't handle this scenario.
Entity Framework - default values doesn't set in sql server table
newid() should work.
See images below:
You have another issue there.
Related
This question already has answers here:
Entity Framework and SCOPE_IDENTITY
(4 answers)
Closed 5 years ago.
I am inserting records in database using stored procedures like below
db.Database.ExecuteSqlCommand("sp_insertNewRecord");
Now I want to get the Id of last inserted record.
Due to some reason I can't use below function
db.TableName.Add(record);
db.SaveChanges();
So please don't suggest me to use this.
Create an output variable in your stored procedure like
create procedure [dbo].[Procedurename] #returnVal int output
as
SET #returnVal = SCOPE_IDENTITY();
After inserting the record get the SCOPE_IDENTITY() and set that into an OUTPUT variable.
and get the id in entity framework while calling stored procedure.
Hope this help!
This question already has answers here:
Entity Framework - stored procedure return value
(5 answers)
Closed 5 years ago.
The problem is that many Stored Procedure must be return status code.
Which marked as
RETURN #status
so the EF (6.x) didn't recognize return type and SP call returns modified rows count (e.g 1,2 etc.)
The workaround to replace RETURN to SELECT is impossible
Change EF call to ADO.NET IMPOSSIBLE
So there is any workaround to get right value from SP without modifying SP
I am guessing you are using database approach. From the designer you can specify the return type of the stored procedure. Refer to this question here for more details how to do that.
Keep in mind that you wont need return part, just put in there select #status
This question already has answers here:
Adding a column to all user tables in t-sql
(2 answers)
Closed 6 years ago.
I created a C# app with a SQL Server 2014 backend. I was only intending to use the app for myself but now I have interest from other users. I never had the forethought to add a user id to any of the tables and my question is how could generate a script to add a uniqueid column to all the tables. I don't want to create a new database for every user and would prefer that every table has a unique column for the user.
Try this :
exec sp_msforeachtable 'alter table ? add new_guid uniqueidentifier null';
This question already has answers here:
Identity increment is jumping in SQL Server database
(6 answers)
Closed 6 years ago.
I have a table in EntityFramework that has a field named by ID,
this field is primary key and is Identity.
when i add records into this table, this field value increases per recor, after adding several records, this value suddenly increases
For example, increased from 90 in 1010
While no transaction has been unsuccessful.
what is the problem?
If you are using Azure SQL this can just happen. We had it happen a few times. It is just the nature of how Azure sql works.
See this question Windows Azure SQL Database - Identity Auto increment column skips values it goes into a detailed explanation for a case very similar to yours
This question already has an answer here:
SQLite handling of NULL
(1 answer)
Closed 7 years ago.
Can anyone confirm that this is a bug?
CREATE TABLE meta
meta_id INTEGER PRIMARY KEY,
localAbsPathAndName TEXT,
purgeGUID TEXT
);
INSERT INTO meta (localAbsPathAndName) VALUES ('C:\some\path');
INSERT INTO meta (localAbsPathAndName) VALUES ('C:\some\path');
SELECT * FROM meta WHERE purgeGUID!='aa5de571c9da5e3995b63427f5d23aad'
incorrectly returns no rows.
purgeGUID is null so Sqlite works correctly because
null != 'aa5de571c9da5e3995b63427f5d23aad' is null
Condition "where null' is never fulfilled
There are 3 columns in your 'meta' table but you provide only one value in insert query.Provide the 3 values and try again it works