Author: yuval

Categories
Web Development

Displaying DHTML over Flash

From my friend Rob Rolsma‘s findings:

To display a DHTML over a Flash object the Flash object must have its window mode set to transparent. This is achieved by setting the “wmode” parameter for the object tag AND the embed tag.

Within the object element for the Flash object include the following element:

<param name="wmode" value="transparent" />

Within the embed element for the Flash object, include the following attribute:

wmode="transparent"

Share
Categories
Computing

Changing CVS repository path in CVS

I am using Eclipse’s CVS module for the project I am currently working on and using the really nice cvsdude.org service for storage.

We upgraded our account to one that gave us our own cvsroot directory and hence had to change the repository path for our project in Eclipse. Eclipse 2.1, does not let you do that. You can update the user name, URL, password, but not the path. Even removing the repository did not do the job.
What did work was:

  1. In Eclipse: Right-click the root folder for the project and choose ‘Disconnect…’ from the ‘Team’ submenu’
  2. Close Eclipse
  3. Start your favorite text editor (one that worked for the procedure below was the free and fabulous jEdit)
  4. Run a global search and replace in the editor to find all instance of the old repository path string and replace them with the new repository path. The search and replace should only be run in the directory of the project. For example, my old path was /cvs/stda and I replaced it with /cvs/newpath.
  5. Start Eclipse again
  6. Right click the root folder of the project and select ‘Refresh’
  7. Right click the root folder of the project again and select ‘Share project’ from the ‘Team’ submenu.
  8. Eclipse should now tell you that the project was previously shared and that it will connect you with the repository. The repository path displayed should now be the correct one – which you updated.
Share
Categories
SQL Server

Transactions not rolling back in SQL Server? How’s your SET XACT_ABORT today?

Every database rookie knows about the ACID principles.
ACID is what makes Oracle snobs look down at MySQL and scoff that it is not a real database.
I am neither a database snob nor an absolute rookie, but a certain behavior in SQL Server 2000 did baffle me. I would create transactions and they would fail in the middle without rolling back (and atomicity was just like, not there).
Rummaging through the beloved server’s documentation (RTFM, RTFM) discovered this flag and the somewhat hair-raising behavior:

If a run-time statement error (such as a constraint violation) occurs in a batch, the default behavior in SQL Server is to roll back only the statement that generated the error. You can change this behavior using the SET XACT_ABORT statement. After SET XACT_ABORT ON is executed, any run-time statement error causes an automatic rollback of the current transaction. Compile errors, such as syntax errors, are not affected by SET XACT_ABORT.

That is, you need to set your SET XACT_ABORT ON before you execute your transaction.

XC3113n7

Share
Share