LS - some basic questions

Hiya

I'm using a MySQL5 database, which contains a table "Users"

The table is pretty simple  - as this is mostly just to see how things are done in LS :

• UserId (int) primary key
• UserName (varchar20)
• UserPass(varchar20)
• UserTypeId (int) foreign key

LightSpeedContext<DBUnitOfWork> ctx = new LightSpeedContext<DBUnitOfWork>();
            ctx.ConnectionString = "server=MyServer;User Id=MyUser;Pwd=MyPassword;Persist Security Info=True;database=mydatabasename";
            ctx.IdentityMethod = IdentityMethod.IdentityColumn;
            ctx.DataProvider = DataProvider.MySql5;

            using (DBUnitOfWork uow = ctx.CreateUnitOfWork())
            {
                User new_user = new User()
                {
                    UserName = "TEST1",
                    UserPass = "TEST2",
                    UserTypeId = 2                   
                };

                uow.Add(new_user);
               
            }

I've had some experience with LINQ to SQL, so I was expecting something in the lines of InsertOnSubmit/SubmitChanges but it turned out that it's done using the uow.Add()

• The following code had no effect on the database, why ?
• How do I hide the password from the connection string?
• How do I perform update operations?
• How do I perform remove operations?

Add is the equivalent of InsertOnSubmit.  You need to call IUnitOfWork.SaveChanges (our equivalent to SubmitChanges) to commit the pending changes to the database.

Password obfuscation is outside the scope of LightSpeed, but I believe you can do this using encrypted connection strings.  Here's an article about this.

To perform update operations, load the entity, make your changes, and call SaveChanges:

var user = uow.FindById<User>(1);
user.Email = "bob@example.com";
uow.SaveChanges();

To perform remove operations, load the entity, call IUnitOfWork.Remove, and call SaveChanges:

var user = uow.FindById<User>(1);
uow.Remove(user);
uow.SaveChanges();

Adds, updates and Removes can of course all be queued up and will be performed in a batch when you call SaveChanges.

Awesome, cheers Ivan.