TRANSACTIONS AND MEMBERSHIP FRAMEWORK

TRANSACTIONS AND MEMBERSHIP FRAMEWORK

Postby JORGEMAL » Mon 24 Nov 2008 23:14

I am developing a web form in Visual Studio 2005 in which a user is added through the membership framework which uses mainly two tables in this case: aspnet_users and aspnet_membership. Besides this 2 tables I need to save additional information about each user like address, first name, last name, phone, fax and other so I have a third table called "users" for this purpose. As you see there are 3 tables involved in this process so I am thinking about using transactions to manage this issue safely. After reading the help files I see that a transaction is based on a connection and the only connection available in my case is the one I define to add the data to the third table because membership tables depend on the CreateUser method of the Membership class.

Is it possible to use transactions and protect the operations on the three tables?
JORGEMAL
 
Posts: 165
Joined: Thu 03 Jul 2008 23:55

Postby AndreyR » Tue 25 Nov 2008 12:29

Unfortunately, there is no way to protect operations on three tables at the moment.
We plan to support TransactionScope (as in dotConnect for Oracle), but no timeframe can be provided.
AndreyR
Devart Team
 
Posts: 2919
Joined: Mon 07 Jul 2008 13:16


Return to dotConnect for PostgreSQL