README for Microsoft Indexed Database Extension for Internet Explorer

 

INTRODUCTION

 

Thank you for choosing to evaluate the Microsoft Indexed Database Extension for Internet Explorer This preview provides an implementation of the Indexed Database API draft of Nov 2nd, 2010 as defined at the following URL: http://html5labs.interoperabilitybridges.com/media/723/indexeddatabaseapi_11022010.htm

 

MINIMUM REQUIREMENTS

 

Microsoft Internet Explorer 9 Beta

 

INSTALLATION / UNINSTALLATION

 

 

To install:
Run vcredist_x86.exe, if you are running 32-bit version of Windows

Run the following commands from an elevated command prompt.
(For instructions on opening an elevated command prompt, see: http://windows.microsoft.com/en-US/windows7/Command-Prompt-frequently-asked-questions)
cd "[path where files were unpacked into]"
regsvr32.exe sqlcejse40.dll

 

To uninstall, close all running instances of Microsoft Internet Explorer and run the following commands from an elevated command prompt window:
cd "[path where files were unpacked into]"
regsvr32.exe /u sqlcejse40.dll
-The following command will also remove all the local databases used
rmdir /q /s "%localappdata%\microsoft\IndexedDatabase"

 

 NOTE: If you have "User Access Control" (UAC) enabled in your computer, in order to use the IndexedDB Prototype you will need to run Internet Explorer in the elevated mode by right clicking on Internet Explorer icon and selecing "Run as Administrator".

To determine if you have UAC enabled in your system, go to Start-->Control Panel-->User Accounts. Invoked "Change User Access Control Setting" to look at the UAC settings. If it is set to anything other than "Never Modify" then UAC is enabled.
 

GETTING STARTED

 

1. Launch the bugTrackerSample.html in your IE browser. You will see the browser warning: "Internet Explorer restricted this webpage from running scripts or ActiveX controls" above the browser status bar. Click on "Allow Blocked Content".

2. Enter bugs and make sure you have bugs distributed across different projects, priority and status.
3. You can use the "Search for existing bugs" section to search by different fields.
4. The result will be a list of links. Clicking on each link will populate the edit section of the page.
5. More fine-grained samples specific to each core IndexedDB operation can be found in the CodeSnippets folder. Launch the html files from this folder to run these samples.

 

KNOWN LIMITATIONS AND DIFFERENCES FROM DRAFT

 

1. In this implementation, VERSION_CHANGE transaction as described in the specification is not implemented.
2. In this implementation, the createObjectStore() method in the asynchronous database object returns an object of type IDBRequest.As per specification, createObjectStore() should return an asynchronous ObjectStore object and should also work within a VERSION_CHANGE transaction.
3. In this implementation, deleteObjectStore() does not work within a VERSION_CHANGE transaction.
4. In this implementation, all delete() methods defined in the specification have been renamed to remove().
5. In this implementation, all continue() methods defined in the specification have been renamed as move().
6. In this implementation, the move() method on the asynchronous cursor object returns an object of type IDBRequest. As per specification it is supposed to return void and call the success handler created when the cursor was opened.
7. In this implementation, the transaction() method in the asynchronous database object takes no parameters. As per specification this method is supposed to take storeNames and an optional timeout duration as parameters.
8. In this implementation, the asynchronous transaction object has a commit() method. As per specification there is no commit() method in the asynchronous transaction object, since commit is implied where the implementation is supposed to keep track of unwinding of event callbacks before committing changes.
9. In this implementation, the update() and delete() methods on the asynchronous cursor object will not work if the cursor is opened through the openCursor() or openKeyCursor() methods of the asynchronous index object.

 

FEEDBACK

 

Microsoft welcomes feedback on this implementation through the following mailing list:

http://mailinglist.interoperabilitybridges.com/scripts/wa-INTEROP.exe?A2=HTML5_INDEXEDDB;a46937c4.1007
You will need to subscribe to the list and then provide feedback.