sqlite-net

I have very simple relationship, my model looks like this: public class Project { [PrimaryKey, AutoIncrement] public int ID { get; set; } public string Name { get; set; } [ForeignKey(typeof(User))] public int ProjectManagerID { get; set; } [ManyToOne] public User ProjectManager { get; set; } } public class User { public string Login { get; set; } [OneToMany] public List<Project> Projects { get; set; } } The problem is that I can easly save project, with its reference to user without saving user, and I don't get any constraint violation exception. database.Insert(new Project { Name = "aaa",

I have installed sqlite-net from NuGet package in my windows phone universal app. But it does not contain foreign key relationship attribute between tables. I searched the web and found that SQLITE-Net Extenstions can handle this by using attributes, But it can only be installed on Windows 8.1 app not on windows Phone 8.1. How can use this extension in windows phone 8.1 or is there any other solution for foreign key relationships in sqlite? Thanks! There exists a PCL version of this library. If you install via NuGet, you might see this error You can solve this by cloning the repository as

I'm currently making an app that needs to store and get data to and from a sqlite database. The two Nuget packages I'm currently using are Sqlite PCL and SQLite-Net Extensions . [Table("patient")] public class Patient { [PrimaryKey] public string ID { get; set;} public string FirstName { get; set; } public string LastName { get; set; } [OneToMany] public List<PatientVitals> PatientVitals { get; set; } } [Table("patientVitals")] public class PatientVitals { [PrimaryKey] public string VitalID {get;set;} public string Weight { get; set;} public string Height { get; set;} [ForeignKey(typeof

I downloaded the package from NuGet and still there's no SQLite.cs neither SQLiteAsync.cs added to the project, If SQLite-NET is still not supporting VS 2015 RTM, Any possible alternatives? Note that I tried SQLite.NET-PCL and still the same problem. SQLite.NET-PCL shouldn't add those two classes directly to your project files. Did you download the right SQLite.NET-PCL via NuGet? (there's a huge mess when you search for SQLite.NET on NuGet so it's easy to get confused and install the wrong one). Did you install the SQLite VSIX package for Universal App Platform development using Visual Studio

I used to open my SQLiteConnection in my shared project as following: var conn = new SQLiteConnection("MyDb.db3"); The constructor has been changed to the following signature: public SQLiteConnection(ISQLitePlatform sqlitePlatform, string databasePath, bool storeDateTimeAsTicks = true, IBlobSerializer serializer = null, IDictionary<string, TableMapping> tableMappings = null, IDictionary<Type, string> extraTypeMappings = null, IContractResolver resolver = null); public SQLiteConnection(ISQLitePlatform sqlitePlatform, string databasePath, SQLiteOpenFlags openFlags, bool storeDateTimeAsTicks =

I am developing a Windows Store App that uses SQLite for Windows Runtime Extension and sqlite-net library to store data in a local SQLite database. This database is created in Windows.Storage.ApplicationData.Current.LocalFolder.Path path. Everything works like it should and I guess I will not have problems when submiting. Question 1 But what will happen when I change the app, submit again and the user updates it? Will database file be deleted? Will the user lost his data? Question 2 Will I be able to use the old database and upgrade it between app versions? I know how to do it when developing

What is the create table statement in SQLite meant to return? I have observed create table if not exists returning both a 0 and 1 when the table does in fact exist. Is the return value a reliable indication of whether the table does exist or not? I would expect the statement to return a 0 if the table already exists and a 1 when it does not, similar to an insert statement. Changes returns the number of affected rows . This values is meaningless for CREATE TABLE statements. There is no easy way to determine whether the CREATE TABLE IF NOT EXISTS statement did the creation or not. You should