Ryan Whitaker - All Comments

re: Transactions with TableAdapters, a lazy man's approach

vikas wadhwa — Fri, 26 Sep 2008 09:33:01 GMT

Thanks for the Code. It was the simplest code I found over net. Easy To implement. Gr8 Work.

re: Highly performant, caching image resizer?

Nathanael Jones — Thu, 07 Aug 2008 17:36:43 GMT

Rescue ship here!

I needed the same thing, so I wrote my own.. and after testing it for 1.5 years, I'm releasing it as a component!

It has a managed disk caching system. When the cache limit is reached, the least used items are cleaned out. Memory and client-side caching are also used.

It supports a variety of image formats, and has a easy syntax:

image.jpg?thumbnail=jpg&maxwidth=100&maxheight=100

The most important thing is that it's rock-solid. We haven't turned up any new bugs in over a year. No memory leaks, crashes, or other issues. And we use it *heavily* on a high traffic site.

Take a look:

nathanaeljones.com/.../asp-net-image-resizer

re: Modify data before it's inserted in SQL Server 2000/2005

Waylon — Wed, 16 Jul 2008 18:59:45 GMT

Have you guys tried a batch update on the table(s) with your proposed triggers active?

re: Transactions with TableAdapters, a lazy man's approach

fabson — Mon, 07 Jul 2008 10:57:55 GMT

very nice code ..i am just about trying it out but please can the fooAdapter still dosomething [i.e fooAdapter.dosomthing] after the baradapter has done something. and do i need to call settransaction again if an already used adapter is to be used again...

Thanks

re: Highly performant, caching image resizer?

Sony Alpha — Sun, 15 Jun 2008 18:16:00 GMT

Thank you very much. this site has provided me with an understanding of caching image resizer

, It's just what I was looking for!

re: Transactions with TableAdapters, a lazy man's approach

Colby — Wed, 04 Jun 2008 03:21:30 GMT

Thanks for the hint..

colbyafrica.blogspot.com/.../microsoft-excel-my-favorite-fallback.html

re: Transactions with TableAdapters, a lazy man's approach

cuongnt@bkav.com.vn — Thu, 08 May 2008 14:44:58 GMT

Thanks a lot for sharing this code!

re: Modify data before it's inserted in SQL Server 2000/2005

Thomas — Sat, 29 Mar 2008 12:10:49 GMT

Exactly what I was looking for, but I have some small adjustments:

USE [RADIUS]

/****** Objekt: Trigger [dbo].[CheckDateTimes] Skriptdatum: 03/29/2008 10:32:52 ******/

SET ANSI_NULLS ON

SET QUOTED_IDENTIFIER ON

-- =============================================

-- Author: <Author,,Name>

-- Create date: <Create Date,,>

-- Description: <Description,,>

-- =============================================

CREATE TRIGGER [dbo].[BusinessEntity_CheckDateTimes]

ON [dbo].[BusinessEntity]

FOR INSERT,UPDATE

BEGIN

-- SET NOCOUNT ON added to prevent extra result sets from

-- interfering with SELECT statements.

SET NOCOUNT ON;

DECLARE @CreateDate DateTime

DECLARE @LastModified DateTime

DECLARE @INDEX Int

SET @CreateDate = (SELECT CreateDate from INSERTED)

SET @LastModified = (SELECT LastModify from INSERTED)

SET @INDEX = (SELECT BusinessEntityIndex from INSERTED)

-- SELECT * INTO #Inserted FROM Inserted

IF (@CreateDate = {ts '1753-01-01 00:00:00.000'})

UPDATE BusinessEntity SET CreateDate = NULL WHERE BusinessEntityIndex = @INDEX

IF (@LastModified = {ts '1753-01-01 00:00:00.000'})

UPDATE BusinessEntity SET LastModify = NULL WHERE BusinessEntityIndex = @INDEX

-- INSERT INTO BusinessEntity SELECT * FROM #Inserted

-- Insert statements for trigger here

END

CREATE TRIGGER [dbo].[Groups_CheckDateTimes]

ON [dbo].[Groups]

FOR INSERT,UPDATE

BEGIN

-- SET NOCOUNT ON added to prevent extra result sets from

-- interfering with SELECT statements.

SET NOCOUNT ON;

DECLARE @Date DateTime

DECLARE @INDEX Int

SET @INDEX = (SELECT GroupIndex from INSERTED)

SET @Date = (SELECT AcctExpireDate from INSERTED)

IF (@Date = '1753-01-01 00:00:00.000')

UPDATE Groups SET AcctExpireDate = NULL WHERE (GroupIndex = @INDEX)

SET @Date = (SELECT AcctStartDate from INSERTED)

IF (@Date = '1753-01-01 00:00:00.000')

UPDATE Groups SET AcctStartDate = NULL WHERE (GroupIndex = @INDEX)

END

CREATE TRIGGER [dbo].[Users_CheckDateTimes]

ON [dbo].[users]

FOR INSERT,UPDATE

BEGIN

-- SET NOCOUNT ON added to prevent extra result sets from

-- interfering with SELECT statements.

SET NOCOUNT ON;

DECLARE @Date DateTime

DECLARE @INDEX Int

SET @INDEX = (SELECT UserIndex from INSERTED)

SET @Date = (SELECT PasswordDate from INSERTED)

IF (@Date = '1753-01-01 00:00:00.000')

UPDATE users SET PasswordDate = NULL WHERE (UserIndex = @INDEX)

SET @Date = (SELECT StartDate from INSERTED)

IF (@Date = '1753-01-01 00:00:00.000')

UPDATE users SET StartDate = NULL WHERE (UserIndex = @INDEX)

SET @Date = (SELECT UserExpiryDate from INSERTED)

IF (@Date = '1753-01-01 00:00:00.000')

UPDATE users SET UserExpiryDate = NULL WHERE (UserIndex = @INDEX)

SET @Date = (SELECT LockoutTime from INSERTED)

IF (@Date = '1753-01-01 00:00:00.000')

UPDATE users SET LockoutTime = NULL WHERE (UserIndex = @INDEX)

END

CREATE TRIGGER [dbo].[UserDetails_CheckDateTimes]

ON [dbo].[userDetails]

FOR INSERT,UPDATE

BEGIN

-- SET NOCOUNT ON added to prevent extra result sets from

-- interfering with SELECT statements.

SET NOCOUNT ON;

DECLARE @Date DateTime

DECLARE @INDEX Int

SET @INDEX = (SELECT UserIndex from INSERTED)

SET @Date = (SELECT CreateDate from INSERTED)

IF (@Date = '1753-01-01 00:00:00.000')

UPDATE UserDetails SET CreateDate = NULL WHERE (UserIndex = @INDEX)

SET @Date = (SELECT LastModify from INSERTED)

IF (@Date = '1753-01-01 00:00:00.000')

UPDATE UserDetails SET LastModify = NULL WHERE (UserIndex = @INDEX)

SET @Date = (SELECT LastTotalOnlineUpdate from INSERTED)

IF (@Date = '1753-01-01 00:00:00.000')

UPDATE UserDetails SET LastTotalOnlineUpdate = NULL WHERE (UserIndex = @INDEX)

END

This makes it easier to maintain for my purpose

re: Transactions with TableAdapters, a lazy man's approach

Matt — Fri, 14 Mar 2008 16:00:39 GMT

David, why did you go to all that effort of making it work within a TransactionScope; is that not what we are trying to get rid of?

re: Transactions with TableAdapters, a lazy man's approach

Mark — Fri, 14 Mar 2008 11:47:38 GMT

Because the commands are not accessible from the outside. You have to create a partial class of a tableAdapter to change their transaction but you end up creating partial classes for all your tableadapters