代码小猪

Knowledge Base Home

a@b.com (bosswin) — Tue, 07 Aug 2007 09:53:49 +0800

Google Code

Open Source

Reach Google Users

Enhance Your Web Site

Integrate With Google

Articles & Tutorials

Google Summer of Code

a@b.com (bosswin) — Mon, 06 Aug 2007 18:09:06 +0800

Google Summer of Code™

Accepted student applications for Google Summer of Code have been announced! We accepted over 900 student applicants from a pool of nearly 6,200 applications.

All the mentoring organizations that will participate in Google Summer of Code 2007 are listed below. You can learn more about the accepted students and their projects by visiting each organization's "about" page.

You might also be interested in keeping up with news about the program on the Google Summer of Code Blog. And, you can still hang out with us in #summer-discuss on Slashnet or in the program discussion group.

Registered Student Login

Registered Mentor Login

You can still take a look at all the organizations' ideas pages to learn more about what help they need from new contributors.

Mentoring Organizations Participating in Google Summer of Code 2007

AbiSource (ideas)

Adium (ideas)

The Apache Software Foundation (ideas)

Aqsis Team (ideas)

Ardour (ideas)

ArgoUML (ideas)

Audacious Media Player (ideas)

Bazaar (ideas)

BBC Research (ideas)

Beagle (ideas)

Blender Foundation (ideas)

Boost C++ (ideas)

BZFlag (ideas)

Center for the Study of Complex Systems (CSCS), University of Michigan (ideas)

CLAM ( at the Universitat Pompeu Fabra) (ideas)

The Codehaus (ideas)

Computer Professionals for Social Responsibility (ideas)

Coppermine Photo Gallery (ideas)

coresystems GmbH (ideas)

Creative Commons (ideas)

Crystal Space (ideas)

Daisy CMS (ideas)

Debian (ideas)

Detached Solutions (ideas)

Django (Lawrence-Journal World) (ideas)

Dojo Foundation (ideas)

Drupal (ideas)

DSpace (ideas)

Eclipse (ideas)

The Electronic Frontier Foundation (ideas)

Etherboot Project (ideas)

eXist (ideas)

FANN - The Fast Artificial Neural Network Library (ideas)

The Fedora Project (ideas)

FFmpeg (ideas)

Fityk (ideas)

The Free Software Initiative of Japan (ideas)

FreeBSD (ideas)

Freenet Project Inc (ideas)

Freevo (ideas)

Gallery (ideas)

GCC (ideas)

The gEDA Project (ideas)

Geeklog (ideas)

GenMAPP (ideas)

Gentoo Foundation (ideas)

The GGI Project (ideas)

Git Development Community (ideas)

GNOME (ideas)

GNU Project (ideas)

GnuCash (ideas)

GNUstep (ideas)

Google (ideas)

Haiku (ideas)

Handhelds.org (ideas)

Haskell.org (ideas)

hugin / panotools (ideas)

IEM - Institute of Electronic Music and Acoustics, Graz (ideas)

ikiwiki (ideas)

Inkscape (ideas)

Internet2 (ideas)

Jikes RVM (ideas)

Joomla! (ideas)

K-3D (ideas)

KDE (ideas)

Lanka Software Foundation (ideas)

Liblime (ideas)

LispNYC.org (ideas)

LLVM Compiler Infrastructure (ideas)

MacPorts (ideas)

maemo (ideas)

MetaBrainz Foundation (ideas)

Mixxx (ideas)

MoinMoin Wiki Project (ideas)

Mono Project (ideas)

Moodle (ideas)

Mozilla Foundation (ideas)

MySQL AB (ideas)

National Evolutionary Synthesis Center (NESCent), Phyloinformatics Group (ideas)

NetBSD (ideas)

Neuros Technology (ideas)

Nmap Security Scanner (ideas)

OGRE (ideas)

One Laptop Per Child (ideas)

Open Security Foundation (OSVDB) (ideas)

Open Source Applications Foundation (ideas)

OpenICC (ideas)

OpenMoko (ideas)

OpenMRS (ideas)

OpenOffice.org (ideas)

OpenSolaris (ideas)

Oregon State University Open Source Lab (OSU OSL) (ideas)

OSCAR (ideas)

OSGeo (ideas)

PHP (ideas)

Pidgin (ideas)

Plan 9 from Bell Labs (ideas)

PlanetMath (ideas)

Plone Foundation (ideas)

Portland State University (ideas)

PostgreSQL project (ideas)

Python Software Foundation (ideas)

Robert H. Lurie Comprehensive Cancer Center of Northwestern University (ideas)

Rockbox (ideas)

Ruby Central, Inc. (ideas)

Samba (ideas)

SCons Foundation: Next-Generation Build Tool (ideas)

Scribus Development Team (ideas)

ScummVM (ideas)

SilverStripe CMS & Framework (ideas)

SIP Communicator (ideas)

The Space Telescope Science Institute (ideas)

Sparse (ideas)

Squeak (ideas)

SquirrelMail (ideas)

Subversion (ideas)

Swarm Development Group (ideas)

Swathanthra Malayalam Computing (ideas)

Taste (ideas)

Thousand Parsec (ideas)

Ubuntu (ideas)

Umit Project (ideas)

VideoLAN (ideas)

Vim (ideas)

Wikimedia Foundation (ideas)

The Wine Project (ideas)

WinLibre (ideas)

WordPress (ideas)

wxPython (ideas)

wxWidgets (ideas)

X.Org (ideas)

Xiph.org Foundation (ideas)

XMMS2 (ideas)

XMPP Standards Foundation (ideas)

XWiki (ideas)

Zope Foundation, Inc (ideas)

We are no longer accepting applications from open source organizations.

If you're feeling nostalgic, you can still access the Google Summer of Code 2005 and Google Summer of Code 2006 pages. We've also created a map (requires Google Earth) of all 2006 mentors and student participants for your perusal.

Questions?

Please peruse our FAQ and Terms of Service for more information about the program. If you still have questions, email us for support

Query API Developer Guide

a@b.com (bosswin) — Sun, 05 Aug 2007 10:55:45 +0800

Query API Developer Guide

Google Desktop indexes, caches, and searches content on your computer. Through the Google Desktop Query API, your applications can send search queries directly to Google Desktop and process its search results.

Getting Started
Registering With the Query API
1. Native Plug-in Registration
2. Script Plug-in Registration
Query Objects
1. Query Methods for Native Plug- Ins
2. Query Methods for Script Plug- Ins
QueryEx Query Objects
1. QueryEx for Native Plug-Ins
2. QueryEx for Script Plug-Ins
Result Objects
1. Result Objects for Native Plug- Ins
2. Result Objects for Script Plug- Ins
Individual Search Result Objects
1. Individual Search Result Objects for Native Plug-Ins
2. Individual Search Result Objects for Script Plug-Ins
Item Versions
1. Item Versions for Native Plug- Ins
2. Item Versions for Script Plug- Ins
HTTP/XML-Based Query API

Getting Started

The Query API described in the first part of this document was introduced with Google Desktop 3. We cover how to use it with both native plug-ins and script-based plug-ins, and assume that you are familiar with the general principles of how to write Desktop plug-ins.

The latter part of this document describes methods for issuing Desktop search queries using HTTP and XML. This XML-based API is supported by both the Windows and Mac OS X versions of Google Desktop. Mac OS X support was added in Google Desktop Mac 1.0.3.

Registering With the Query API

You can only use the Query API if you have registered with it and thus obtained a Query API registration cookie. Note that this is in addition to the general registration of your plug-in with Google Desktop.

There are two types of Query API registration cookies, read-only and read- write. Usually, you'll only need a read-only cookie. The read-write cookie is only needed when you remove an item from the Google Desktop index.

We recommend that your plug-in encrypt the registration cookie when it saves it, and, of course, be able to decrypt it when you pass it to the various Query API methods and objects.

You'll need a global identifier (GUID) for your plug-in to pass to the registration method. You can use a tool such as guidgen.exe to generate one.

Native Plug-in Registration

If you are writing a native plug-in, the following summarizes the registration interface and its method. All method return values are of type HRESULT.

`interface IGoogleDesktopRegisterQueryPlugin: IDispatch`

Note: Components are required to call this interface to register themselves with the Google Desktop Query API before they can make use of that API.

RegisterPlugin: Must be invoked by any component to register with the Query API.
- Arguments:
  - BSTR plugin_class: The component's GUID or ProgID.
  - VARIANT_BOOL read_only: If true, you can do search queries but cannot delete items from the index. A false value gives you both read and write access, allowing you to delete index items.
  - [out, retval] long* cookie : Returns the registration cookie. Save this value, as you will have to use it whenever you make a query or remove an item from the Desktop index via the Query API.
- Returns:
  - S_OK if successful.
  - Appropriate error on failure, such as an unregistered component classID or appID, component prohibited by policy, etc.

Script Plug-in Registration

If you are writing a script-based plug-in, see register_script_sample.js for a complete example of registering with the Query API using JavaScript. The gist is the following code:

try { // Instantiate the Google Desktop registrar component by creating // an ActiveX registration object. var registrar = new ActiveXObject("GoogleDesktop.Registrar"); // Give it our plug-in GUID and description registrar.StartComponentRegistration(g_scriptSampleId, componentDescription); // Ask for the specific registration object that gives us Query API access. var regObj = registrar.GetRegistrationInterface ("GoogleDesktop.QueryRegistration"); // Now ask that registration object to give us a cookie representing // our Query API access. Note the read_only flag argument here; // if false, then we're asking for read-write access instead of // just read-only access. cookie = regObj.RegisterPlugin(g_scriptSampleId, read_only); // Now submit and hope the user will accept this component. // If not, then an error will be thrown registrar.FinishComponentRegistration ();} catch (e) { // We hit an error message("Couldn't register the script samples.\n" + new String(e.number) + "\n" + e.description); return 0;}

Note that you need to save the cookie value, as you will have to use it whenever you make a query or remove an item from the Desktop index via the Query API.

Query Objects

The Query API has one root object, IGoogleDesktopQueryAPI for native plug-ins, GoogleDesktop.QueryAPI for script plug-ins, that supports two methods:

Query: Immediately executes the specified desktop search query and returns a result object that contains all the search results for the query.
QueryEx: Returns a query object which does not (yet) actually execute the query. Instead, you can tweak some custom parameters first, then execute the revised query. When executed, it returns the same type of result object as Query.

The Query and QueryEx root object methods both take the following arguments:

cookie: The security cookie created when you registered your plug-in with the Query API.
query: The search query string, which can include the same set of query operators that you could use in a query typed into a Google Desktop search box.
category: Optional string argument that lets you restrict results to those of a particular type. Valid values are email, web, im, file, contact, calendar, task, note, or journal.
ranking: Optional numeric argument specifying whether the search results will be ranked by date (RECENCY_RANKING = 1), the default, or by relevance (RELEVANCE_RANKING = 0).

Query Methods for Native Plug-Ins

`interface IGoogleDesktopQueryAPI: IDispatch`

Query: Immediately takes the specified search query and executes it with default option values.
- Arguments:
  - long cookie: The component's Query API security cookie.
  - BSTR query: The search query string, which can contain any of the allowed Desktop search operators.
  - VARIANT category: [Optional]
  - VARIANT ranking: [Optional]
  - [out, retval] IGoogleDesktopQueryResultSet** results: The search results from having automatically executed a desktop search for the search query.
- Returns:
  - S_OK if successful.
  - Appropriate error on failure.
QueryEx: Returns a query object that does not automatically execute a search. Instead, you can alter the query's properties and exert finer control over the search, and then execute the query.
- Arguments:
  - long cookie: The component's Query API security cookie.
  - BSTR query: The search query string, which can contain any of the allowed Desktop search operators.
  - VARIANT category: [Optional]
  - VARIANT ranking: [Optional]
  - [out, retval] IGoogleDesktopQuery** q) : An unexecuted query object, which you can alter the default properites and parameters of before running a search on its search query.
- Returns:
  - S_OK if successful.
  - Appropriate error on failure.

Query Methods for Script Plug-Ins

In JavaScript, you just create the base object and then create and run the Query in one step.

// Instantiate the main query api objectvar qapi = new ActiveXObject ("GoogleDesktop.QueryAPI");// Perform the query and get a recordset object back containing the// search results.var set = qapi.Query(cookie, search_string);

See the simple_query.js example for a detailed example.

QueryEx Query Objects

If you run the QueryEx() method, it returns a Query object for which you can change any or all of these four options before executing the query:

async: By setting this to false, all result items are fetched before the Execute() method completes. The default value is true.
filter_duplicates: By setting to false, you'll get all the items that match, including any duplicates of already matched items. Default is true.
match_all_terms: When set to false, if there are multiple query terms, any item matching just one of the query terms is returned. Otherwise, a result must match all of the query terms. Default is true.
blacklisting: By setting to false, items in the search results do not go through the default blacklisting filters. Default is true. If you turn this off, you'll most likely see spam email, secure content, bad urls such as about:, res:, etc. in addition to your good results.

To change an option value, use the SetOption() method, one of four methods associated with Query objects. These are:

SetOption: Takes arguments, in this order, of what option to set and what value to set it to.
GetOption: Takes an option name, returns its value.
query: Takes no arguments, returns a string containing the search query.
Execute: Once you've finished setting the Query object's options, run this method to actually run the search. Returns a query result set.

QueryEx for Native Plug-Ins

QueryEx's returned object, IGoogleDektopQuery, has the following interface:

`interface IGoogleDesktopQuery: IDispatch`

SetOption: Set an option value.
- Arguments:
  - BSTR name: Which option to set.
  - VARIANT value: What value to set the option to.
- Returns:
  - S_OK if successful.
  - Appropriate error on failure.
GetOption: Get an option value.
- Arguments:
  - BSTR name: Which option to get the value of.
  - [out, retval] VARIANT* value: The option's value.
- Returns:
  - S_OK if successful.
  - Appropriate error on failure.
query: Get the search query string.
- Arguments:
  - [out, retval] BSTR* ret: The search query string.
- Returns:
  - S_OK if successful.
  - Appropriate error on failure.
Execute: Execute the search as specified by the QueryEx object's query string and option values.
- Arguments:
  - [out, retval] IGoogleDesktopQueryResultSet** results: Results from the search.
- Returns:
  - S_OK if successful.
  - Appropriate error on failure.

QueryEx for Script Plug-Ins

The following code using QueryEx comes from the item_count.js example. It shows the usual series of events when using QueryEx; call QueryEx on the base Query API object to get a Query object, set Query object options with SetOption(), then call Execute() on the Query object and get back a recordset of the search results.

var q = new ActiveXObject("GoogleDesktop.QueryAPI");// Call the QueryEx method so that we can turn off the asynchronous// loading of record items.var qx = q.QueryEx (g_securityCookie, query);// Turn off the default asynchronous behavior.qx.SetOption ("async", false);// Execute the query synchronously and get back a recordset objectvar set = qx.Execute();

Result Objects

When you execute a Query or QueryEx, it returns a result set object. This object contains individual result item objects, each of which represents a single search result.

Unless you used QueryEx and changed the default value of the Query object's async option to false from its default value true before executing the query, you can access search results before the search has completely finished. To find out if a search has completed, check the resultset's readystate property, which can have three values:

GD_QRS_UNITIALIZED = 0: Search has not yet started.
GD_QRS_LOADING = 1: Search is still in progress.
GD_QRS_COMPLETE = 2: Search is complete, with all results received and in the resultset.

There are four methods associated with result set objects:

readystate: Takes no arguments, returns the current readystate value.
count: Takes no arguments, returns the total number of individual search result items in the recordset. Note that this number will change as long as results are still arriving. Until readystate is GD_QRS_COMPLETE, this value is an estimate.
Next: Takes no arguments, returns the next individual search result in the set. If results are still arriving and Next() is at the end of the current results, it will wait until the next result arrives. If you reach the end of the results after all results are in the recordset, Next() returns null.
available_count: Takes no arguments, returns how many individual results can be fetched via calls to next() without it blocking while waiting for more results.

Result Objects for Native Plug-Ins

`interface IGoogleDesktopQueryResultSet: IDispatch`

Next: Returns the next individual search result in the set. If results are still arriving, it waits for the next result to arrive before returning it. If called after reaching the final result, it returns S_FALSE and null.
- Arguments:
  - [out, retval] IGoogleDesktopQueryResultItem** next: An individual search result.
- Returns:
  - S_OK if successful.
  - S_FALSE and null if called after the last result has already been returned.
  - Appropriate error on failure.
readystate: Returns the current readystate value, which can be
- GD_QRS_UNINITIALIZED = 0
- GD_QRS_LOADING = 1 (Still receiving results)
- GD_QRS_COMPLETE = 2 (All results received)
- Arguments:
  - [out, retval] QRSReadyState* state: readystate's value.
- Returns:
  - S_OK if successful.
  - Appropriate error on failure.
count: Returns the total number of individual search result items. Note that this number will change so long as individual results are still arriving. Until the readystate value becomes GD_QRS_COMPLETE, this value is an estimate. After that, it is the exact and total number of individual search results.
- Arguments:
  - [out, retval] long* ret: Number of results
- Returns:
  - S_OK if successful.
  - Appropriate error on failure.
available_count: Returns the value of how many individual results can currently be fetched via calls to next() without blocking.
- Arguments:
  - [out, retval] long* available_count : Current remaining number of available search results.
- Returns:
  - S_OK if successful.
  - Appropriate error on failure.

Result Objects for Script Plug-Ins

To iterate through a result set's individual results in JavaScript, you'd write something like:

var item;while ((item = results.Next()) != null) { // process item here}

Individual Search Result Objects

Result item objects each contain a single search result. The key method is GetProperty, which takes a property name and returns its value for the result. The complete list of valid property names is quite long; the ones you'll probably use most often are content, uri, summary, and for email from, to, and subject.

To avoid errors due to trying to get a value for a property that doesn't exist for a result type (for example, a file doesn't have a from property), you should first use the schema method to determine the result's type. The following schemas are defined in the Desktop SDK IDL:

    "web" 
    "text" 
    "media" 
    "office" 
    "file" 
    "calendar" 
    "contact" 
    "email" 
    "im" 
    "note" 
    "journal" 
    "task" 
    "shortcut"

If you try to get a value for a property the result doesn't have, an error is returned. For scripts, that means an exception is thrown, so remember to use exception handling in your script plug-ins.

There are four methods associated with result item objects:

GetProperty: Takes a property name argument, returns that property's value.
schema: Takes no arguments, returns the name of the item's schema.
versions: Takes no arguments, returns either a list of emails in this item's thread (if the item is an email) or a list of all file versions (if the item is a file) in the Desktop index. These are returned as a document versions object.
RemoveFromIndex: Takes one argument, which if true (the default value) removes this item and all its versions from the Desktop index. If false, only this individual item is removed. Remember, you must have a read-write Query API registration cookie for this method to work. If you don't have one, you'll get an "Access Denied" error.

The complete property set is:

actual_work
album_title
artist
assistant
attendees
author
bcc
birthday
bit_rate
bookmarked
buddy_name
business_address
business_fax
business_home_page
business_phone
categories
cc
channels
children_names
comment
companies
company
company_name

company_phone
component_guid
component_id
content
conversation_id
cookie
cookie_raw
country
data_rate
date
date_completed
department
display_name
doc_id
due_date
duration
email1
email2
email3
end_date
event_id
extra_binary_data
extra_data

flags
folder_name
format
from
genre
height
hobbies
home_address
home_fax
home_phone
im_address
importance
info_tip
interaction_period
internet_shortcut_name
job_title
keywords
language
last_modified_time
length
location
lyrics
machine_name

mail_flags
mail_header
mail_id
manager_name
message_time
mobile_phone
native_size
nickname
office_location
organizer
original_date
other_address
other_phone
owner
pager
participants
percent_complete
personal_home_page
primary_fax
primary_phone
profession
received
recurrence_pattern

replyto
shortcut_target
spouse
start_date
start_time
status
subject
text_content
thumbnail
thumbnail_format
timestamp
title
to
total_work
track_number
type
uri
user_name
web_page
wedding_anniversary
width
year_published

Individual Search Result Items for Native Plug-ins

The following is the interface for IGoogleDesktopQueryResultItem, the native plug-in individual result item.

`interface IGoogleDesktopQueryResultItem: IDispatch`

GetProperty: Looks up and returns property values.
- Arguments:
  - BSTR prop_name: Property name to look up the value of.
  - [out, retval] VARIANT* value : Value of the property argument for this result.
- Returns:
  - S_OK if successful.
  - Appropriate error on failure.
RemoveFromIndex: Removes either only this item or all versions of this item from the Desktop index (for email items, the latter means removing all messages in its thread). Note that you must have a read-write Query API registration cookie for this method to work; if not you'll get an "Access Denied" error.
- Arguments:
  - VARIANT_BOOL remove_all_related_versions : If VARIANT_TRUE, all versions are removed. If VARIANT_FALSE, only this single item is removed.
- Returns:
  - S_OK if successful.
  - Appropriate error on failure.
schema: Returns the name of the item's schema.
- Arguments:
  - [out, retval] BSTR* schema_name : Name of this item's schema
- Returns:
  - S_OK if successful.
  - Appropriate error on failure.
versions: Returns either a list of emails in this item's thread (if the item is an email) or a list of all file versions (if the item is a file) in the Desktop index.
- Arguments:
  - [out, retval] IGoogleDesktopDocumentVersions** ret: List of item's versions or other messages in its thread.
- Returns:
  - S_OK if successful.
  - Appropriate error on failure.

Individual Search Result Items for Script Plug-ins

The following code from the lucky.js example shows how to get various properties from each individual result item in a result set. The message() method is a basic output method defined early in the script.

//Get the next individual search result item from the recordset var item = set.Next()if (item != null) { // First output the URI of the item we found message(item("uri")); // Now output the text representation of the content message(item("text_content")); // Alternatively, we could output the content in its native form // message(item ("content"));} else { message("no item found!");}

The remove_from_index.js example shows first how to build a query whose results are restricted by being a specific filename in a specific folder, as well as a script that removes from the Desktop index all result items from a search query.

Item Versions

The result item's version property requires a bit of explanation. Its value is a document versions object, which is a collection of individual query result items. These are the same individual result items described in the previous section; in other words, an individual search result object can contain other individual result objects in its version property.

For an email message, its version contents are the other email messages in the same thread. For a file, its version contents are any other versions of that file, either from an earlier or a later time, indexed by Desktop.

The method of accessing individual versions is different from how individual results are gotten from a search result recordset. The count property's value is the number of versions in the document versions object. The Item() method takes a 0-based index value and returns the result item object at that location. Note that the versions are not ordered other than by their index value; version 0 is not necessarily the earliest or latest version, version 1 may be earlier or later than version 0, etc.

Item Versions in Native Plug-ins

`interface IGoogleDesktopDocumentVersions: IDispatch`

count: Number of separate versions in this object.
- Arguments:
  - [out, retval] long* ret : Number of indexed versions of this item.
- Returns:
  - S_OK if successful.
  - Appropriate error on failure.
Item: Takes an index value and returns the result item stored at that location in the document versions list.
- Arguments:
  - long index : Index value of the version to be returned.
  - [out, retval] IGoogleDesktopQueryResultItem** ret: The item at the position provided by the index argument.
- Returns:
  - S_OK if successful.
  - Appropriate error on failure.

Item Versions in Script Plug-ins

The versions collection has one function, Item(index) and one property, count, which function as described above.

HTTP/XML-Based Query API

Getting Started

From here to the end of the document, we cover how to use the HTTP/XML-based Query API.

To issue Google Desktop HTTP/XML search queries you will need to know, in addition to the information in this document:

How to issue an HTTP request.
How to process an XML-format HTTP response.

Requesting a Desktop Search

Your application requests a desktop search by sending an HTTP request that includes a &format=xml parameter to Google Desktop. For example, to search for "Google" you'd send something like:

http://127.0.0.1:4664/search&s=1ftR7c_hVZKYvuYS-RWnFHk91Z0? q=Google&format=xml

To break this down:

http://127.0.0.1:4664/ is the localhost address and Google Desktop port.
search&s=1ftR7c_hVZKYvuYS-RWnFHk91Z0 is the search command and a security token.
?q=Google is the query term(s) parameter.
- If you want to search for more than one term, separate the terms with +s. For example, to search for both "Google" and "Desktop", use:
  ?q=Google+Desktop
- If you want to search for a specific phrase, separate the terms with +s and surround the phrase with %22s. For example, to search for the phrase "Google Desktop", use:
  ?q=%22Google+Desktop%22
  
  To search for the two phrases "Google Desktop" and "Copyright 2007", use:
  ?q=%22Google+Desktop%22+%22Copyright+2007%22.
&format=xml specifies that the HTTP response returns the search results in XML format, as described in the next section.

Note: These requests perform only a desktop search, not both a web and desktop search.

By default, an HTTP search response will only return the first ten results. You can specify a larger number by appending the &num= parameter, followed by the maximum number of results you'd like returned, to your query. There is no problem if the maximum number argument value is greater than the total number of search results; only the total number of results is returned, with no null "results".

You can also specify at what point in the results the returned ones start. For example, if you're using the default value of 10 returned results and want to get back results 11-20 instead of the default results 1-10, append the &start= parameter, followed by the position you want the results to start from. In this example, you'd specify &start=10 to indicate you want your returned results to start with the one after overall result 10. The &start= and &num= parameters can both be used in a single query.

To create a query, first get the query URL that Google Desktop stores. Then append your query terms, any optional parameters, and the &format=xml parameter.

Getting the Stored Query URL

The stored query URL has the first part of the URL that you need to perform any Google Desktop query. It looks something like the following:

http://127.0.0.1:4664/search&s=1ftR7c_hVZKYvuYS-RWnFHk91Z0?q=

How you get the stored query URL depends on whether your code is running on Windows or Mac OS X.

Windows

Get the query URL from the registry using the following value name:

HKEY_CURRENT_USER\Software\Google\Google Desktop\API\search_url

Mac OS X

Use CFPreferences to fetch the stored query URL from the user preferences domain com.google.Desktop.WebServer using the key search_url. For example:

CFStringRef val = CFPreferencesCopyValue( CFSTR("search_url"), CFSTR ("com.google.Desktop.WebServer"), kCFPreferencesCurrentUser, kCFPreferencesAnyHost);if (val) { // act on the value CFRelease(val);}

Desktop Search Results

When a search request has the &format=xml parameter, Google Desktop returns results in an XML format. For example:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ? ><results count="24945"><result> <category>web</category>  <title>Developer Knowledge Base - Read the Google Desktop blog</title> <url>http://code.google.com/support/bin/answer.py?answer=66869&topic=10434</url> <time>128243290079530000</time> <snippet>Desktop engineers regularly post development articles and announce updates to the <b>SDK</b> and documentation. Here are some interesting posts from the past: New</snippet> <thumbnail>/thumbnail?id=6% 5Fvwps3QA4FIYGAAAA&s=wgQCmjGl0VEzw3KVhm3mxBG_x48</thumbnail> <icon>/icon? id=http%3A%2F%2Fcode%2Egoogle%2Ecom%2F&s=kKR1by-QXDMlb5vEhxkDZhCv3eE</icon> <cache_url>http://127.0.0.1:4664/...</cache_url> </result>...</results>

The one meta-results tag is <results>, which contains the total number of items that matched the query as the value of a count parameter; e.g. <results count=42>. This will be the largest number of possible <result>...</result> entries in the <results> element. However, if the number of returned results (which defaults to at most 10 if you don't specify an &num= parameter with a larger value) is different from the count value, the number of returned <result>...</result> entries will be the smaller of the two conflicting values.

For example, let's say the <count> value is 42. But you didn't give an &num= argument in the query. So, despite there being 42 items that matched the query, the XML response will only contain 10 <result>...</result> entries. If the <count> value was 6, which is smaller than the default 10 value, the XML response will only contain 6 <result>...</result> entries.

If you want to be sure to obtain all search results, your component will have to parse out the <count> value and then issue additional HTTP Google Desktop search requests to retrieve that many results via use of either the &start= or &num= parameters.

Each <result> may include the following fields, which may appear in any order. Which fields appear will depend on the result type; for example, the <from> entry should only show up in email or chat results. Each tag will contain a value; any tags not containing a value are not shown.

<cache_url> is the Google Desktop-relative URL of this result's internal cache page.

<category> contains the result's type. The following table shows the possible result types for each platform.

Result Type	Windows	Mac OS X
application
bookmark
calendar
chat
contact
email
file
journal
media_file
note
task
web

<folder> is the name of the folder containing an email message. This field is not used on Mac OS X.
<from> is the name of either the person an email message was from, or the other party in an Instant Message chat.
<icon> is a Google Desktop-relative URL to an icon representing this result or its type. This will either be one of the standard Google Desktop Search result type icons (envelope for email, Word icon for a Word file, etc.) or a favicon obtained from a website.
<snippet> is a snippet from the result's content that contains at least one of the search terms.
<thumbnail> is a relative URL to the icon for this result at the Google Desktop webserver
<time> is the time value from the event that put this content into Google Desktop. Usually this will be the time the content was indexed by Google Desktop, but, for example, it could also be a file's last modified time. The format is per the Windows FILETIME structure; the number of 100-nanosecond intervals since January 1, 1601 represented as a 64-bit number.
<title> is the result's title, which varies depending on its type, for example:
- Web page: the page's title.
- Email: the message's Subject:.
- File: its filename.
- Chat: a line from the chat.
<url> is the result's URL. For files and web pages, this is the usual path to the result. For chats and email messages, Google Desktop generates a URL for the location where it has stored its cached copy.

If you want to experiment with queries to see what their XML format results look like, just do a desktop search from the browser. Then append ?format=xml to the result's URL, hit Enter, and the same results will display in XML format in the browser. Two caveats: first, only the number of results that originally appeared on one results page will show up in the browser in XML. So, for example, if only 10 HTML format results show up in the browser on one results page, only 10 XML format results will appear in the browser, even if the value of the <results> tag's count parameter is, say, 42. Second, your browser must include an XML viewer, which IE and Firefox do by default.

Finally, note that the XML results do not include the search terms. If your application wants to also make use of the search terms, as well as the results, it will have to keep track of what they were.

.Net反编译工具Reflector

a@b.com (bosswin) — Thu, 05 Jul 2007 13:21:56 +0800

.Net非常不错的反编译工具Reflector，用它打开.exe.mcl.dll文件可以查看到这些文件的源代码（要.NET开发的哦）

下载地址：Reflector

.NET模板引擎 (代码生成器静态页生成生成HTML 模板)

a@b.com (bosswin) — Wed, 04 Jul 2007 21:30:48 +0800

CodeGenerator 的特点:
1. 标记简结实用, 所有网页美工都能在一分钟内掌握. 而且不与HTML标准冲突, 模板页可用任何WYSIWYG工具编辑, 和编辑普通HTML网完全相同.
2. 标记只与表示层相关, 不包括任何业务逻辑, 丝毫不影响你应用多层结构.
3. 标记到后台被解析成了生成器对象, 完全面向对象, 不像绝大多数生成器要死嗑字符串.
4. 生成器对象使用DataSource属性取得数据, DataSource可以为简单值类型(如 int, DateTIme), 也可以为简单数组(如 decimal[], string[]), 还可以为ADO.NET数据集(如DataTable), 甚至单个对象实体或对象集合或列表(如 SomeClassCollection, List<SomeClass>), 所有数据源类型通吃! 哈哈, 比ASP.NET带的数据控件支持的类型还多.
5. 标记的Name直接与数据源的列名ColumnName或属性名PropertyName, 好处不言而喻了吧.
6. 说到这里好了, 留一手先. 呵呵

演示地址: http://efplatform.net/demo/codegenerator/default.aspx
EFPlatform.CodeGenerator.dll 下载地址: 200707042135476872.rar

应用流程:

Default.aspx.cs:

using System;
using System.Collections.Generic;
using System.Configuration;
using System.Data;
using System.Data.Common;
using System.IO;
using System.Text;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using EFPlatform.CodeGenerator;

public partial class _Default : Page
{
    private string outputPath;
    private string categoryFileName;
    private string productFileName;
    private static DbProviderFactory dbFactory;
    private DbConnection connection;

    protected void Page_Load(object sender, EventArgs e)
    {
        outputPath = Server.MapPath("./");
        categoryFileName = string.Format(@"{0}\Template\Category.html", outputPath);
        productFileName = string.Format(@"{0}\Template\Product.html", outputPath);
        string currentConnection = ConfigurationManager.AppSettings["Connection"];
        ConnectionStringSettings css = ConfigurationManager.ConnectionStrings[currentConnection];
        this.GetConnection(css);
    }

    private void GenerateCategory()
    {
        string template = Helper.ReadTextFile(categoryFileName);
        Generator gen = new Generator(template);
        gen.ParseTemplate();
        Region rgnTitle = gen.Regions["Title"];
        Region rgnCategory = gen.Regions["Category"];
        Region rgnProducts = gen.Regions["Products"];
        Region rgnNavigator = gen.Regions["Navigator"];

        if(rgnTitle == null || rgnCategory == null || rgnProducts == null || rgnNavigator == null)
        {
            Response.Write("Missing region.");
            return;
        }

        int categoryId;
        string outputFileName;
        DataView dvCategory = this.GetCategoryTable().DefaultView;
        Pager pgrCategory = new Pager(1, dvCategory.Count);

        for(int i = 0; i < pgrCategory.PageCount; i++)
        {
            rgnTitle.DataSource = (string)dvCategory[i]["CategoryName"];        //Use a string as data source
            rgnCategory.DataSource = dvCategory[i];        //Use a DataRowView object as data source
            pgrCategory.CurrentPage = i + 1;
            rgnNavigator.DataSource = pgrCategory;        //Use a Pager object as data source
            categoryId = (int)dvCategory[i]["CategoryID"];
            rgnProducts.DataSource = this.GetProductTable(categoryId);        //Use a DataTable object as data souce
            outputFileName = string.Format(@"{0}\Html\Category{1}.html", outputPath, categoryId);
            Helper.WriteTextFile(outputFileName, gen.Generate());
        }
    }

    private void GenerateProduct()
    {
        string template = Helper.ReadTextFile(productFileName);
        Generator gen = new Generator(template);
        gen.ParseTemplate();
        Region rgnTitle = gen.Regions["Title"];
        Region rgnProduct = gen.Regions["Product"];
        Region rgnNavigator = gen.Regions["Navigator"];

        if(rgnTitle == null || rgnProduct == null || rgnNavigator == null)
        {
            Response.Write("Missing region.");
            return;
        }

        string outputFileName;
        List<Product> productList = this.GetProductList();
        Pager pgrProduct = new Pager(1, productList.Count);

        for(int i = 0; i < pgrProduct.PageCount; i++)
        {
            rgnTitle.DataSource = productList[i].CategoryName;        //Use a string as data source
            rgnProduct.DataSource = productList[i];        //Use a Product object as data source
            pgrProduct.CurrentPage = i + 1;
            rgnNavigator.DataSource = pgrProduct;        //Use a Pager object as data source
            outputFileName = string.Format(@"{0}\Html\Product{1}.html", outputPath, productList[i].ProductID);
            Helper.WriteTextFile(outputFileName, gen.Generate());
        }
    }

    #region DataSourcePreparing
    private void GetConnection(ConnectionStringSettings css)
    {
        if(dbFactory == null)
        {
            dbFactory = DbProviderFactories.GetFactory(css.ProviderName);
        }

        this.connection = dbFactory.CreateConnection();
        this.connection.ConnectionString = css.ConnectionString;
    }

    private DataTable GetCategoryTable()
    {
        string commandText = "SELECT CategoryID, CategoryName, Description FROM Categories";
        DbDataAdapter da = dbFactory.CreateDataAdapter();
        da.SelectCommand = dbFactory.CreateCommand();
        da.SelectCommand.Connection = this.connection;
        da.SelectCommand.CommandText = commandText;
        DataTable dt = new DataTable();
        this.connection.Open();
        da.Fill(dt);
        this.connection.Close();
        return dt;
    }

    private DataTable GetProductTable(int categoryId)
    {
        string commandText = string.Format("SELECT * FROM Products WHERE CategoryID = {0}", categoryId);
        DbDataAdapter da = dbFactory.CreateDataAdapter();
        da.SelectCommand = dbFactory.CreateCommand();
        da.SelectCommand.Connection = this.connection;
        da.SelectCommand.CommandText = commandText;
        DataTable dt = new DataTable();
        this.connection.Open();
        da.Fill(dt);
        this.connection.Close();
        return dt;
    }

    private List<Product> GetProductList()
    {
        string commandText = "SELECT p.*, c.CategoryName, s.CompanyName FROM (Products AS p INNER JOIN Categories AS c ON p.CategoryID = c.CategoryID) INNER JOIN Suppliers AS s ON p.SupplierID = s.SupplierID ORDER BY p.ProductID";
        DbCommand command = this.connection.CreateCommand();
        command.CommandText = commandText;
        List<Product> productList = new List<Product>();
        Product product;
        this.connection.Open();

        using(DbDataReader dr = command.ExecuteReader())
        {
            while(dr.Read())
            {
                product = new Product();
                Helper.FillModel(product, dr);
                productList.Add(product);
            }
        }

        this.connection.Close();
        return productList;
    }

    private class Product
    {
        private int productID;

        public int ProductID
        {
            get { return productID; }
            set { productID = value; }
        }

        private string productName;

        public string ProductName
        {
            get { return productName; }
            set { productName = value; }
        }

        private string companyName;

        public string CompanyName
        {
            get { return companyName; }
            set { companyName = value; }
        }

        private int categoryID;

        public int CategoryID
        {
            get { return categoryID; }
            set { categoryID = value; }
        }

        private string categoryName;

        public string CategoryName
        {
            get { return categoryName; }
            set { categoryName = value; }
        }

        private string quantityPerUnit;

        public string QuantityPerUnit
        {
            get { return quantityPerUnit; }
            set { quantityPerUnit = value; }
        }

        private decimal unitPrice;

        public decimal UnitPrice
        {
            get { return unitPrice; }
            set { unitPrice = value; }
        }

        private int unitsInStock;

        public int UnitsInStock
        {
            get { return unitsInStock; }
            set { unitsInStock = value; }
        }

        private int unitsOnOrder;

        public int UnitsOnOrder
        {
            get { return unitsOnOrder; }
            set { unitsOnOrder = value; }
        }

        private int reorderLevel;

        public int ReorderLevel
        {
            get { return reorderLevel; }
            set { reorderLevel = value; }
        }

    }
    #endregion

    protected void Button1_Click(object sender, EventArgs e)
    {
        this.GenerateCategory();
    }

    protected void Button2_Click(object sender, EventArgs e)
    {
        this.GenerateProduct();
    }
}

Web.config:

<?xml version="1.0"?>
<configuration>
    <system.web>
        <compilation debug="true" />
        <authentication mode="Windows" />
        <customErrors mode="Off" defaultRedirect="GenericErrorPage.htm">
            <error statusCode="403" redirect="NoAccess.htm" />
            <error statusCode="404" redirect="FileNotFound.htm" />
        </customErrors>
    </system.web>
    <connectionStrings>
        <add name="Access" providerName="System.Data.OleDb" connectionString="Provider=Microsoft.Jet.OLEDB.4.0;Data Source=|DataDirectory|Northwind.mdb"/>
        <add name="SqlExpress" providerName="System.Data.SqlClient" connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;Database=Northwind;AttachDBFilename=|DataDirectory|Northwind.mdf"/>
    </connectionStrings>
    <appSettings>
        <add key="Connection" value="Access"/>
    </appSettings>
</configuration>

转载：Eric's Bloggy

Eric 的随机文件名生成方法

a@b.com (bosswin) — Wed, 04 Jul 2007 21:27:18 +0800

利用当前时间与2000-1-1 0:0:0 相差的毫秒数转成36进制字符串加上4位随机字符串生成一个随机文件名. 算是长度比较短而唯一性比较高的随机文件名生成方法了.

实测1,000,000 * 100次, 平均每生成1,000,000个随机文件名耗时0.3秒. (测试平台:Dell 640M, T2300, XPSP2)

private static string charDictionary = "0123456789abcdefghijklmnopqrstuvwxyz";

#region GetRandomString
public static string GetRandomString(int length)
{
    return GetRandomString(new Random(), length);
}

public static string GetRandomString(string dictionary, int length)
{
    return GetRandomString(new Random(), dictionary, length);
}

public static string GetRandomString(Random r, int length)
{
    return GetRandomString(r, charDictionary, length);
}

public static string GetRandomString(Random r, string dictionary, int length)
{
    if(r == null)
    {
        r = new Random();
    }

    StringBuilder sb = new StringBuilder();
    char[] chars = dictionary.ToCharArray();

    for(int i = 0; i < length; i++)
    {
        sb.Append(chars[r.Next(0, chars.Length)]);
    }

    return sb.ToString();
}
#endregion

#region GetRandomFileName
public static string GetRandomFileName()
{
    return GetRandomFileName(new Random());
}

public static string GetRandomFileName(Random r)
{
    long timeSpan = (long)(DateTime.Now - new DateTime(2000, 1, 1)).TotalMilliseconds;
    string fileName = ConvertToRadix(timeSpan, 36);
    fileName += GetRandomString(r, 4);
    return fileName.ToLower();
}
#endregion

#region ConvertToRadix
public static string ConvertToRadix(long number, byte scale)
{
    if(scale < 2 || scale > 36)
    {
        throw new Exception("Scale number must not be less than 2 and bigger then 36.");
    }

    char[] dictionary = charDictionary.ToCharArray();
    List<char> charList = new List<char>();
    long positive = Math.Abs(number);

    for(int i = 0; i < 64; i++)
    {
        if(positive == 0)
        {
            break;
        }

        charList.Add(dictionary[positive % scale]);
        positive /= scale;
    }

    charList.Reverse();
    return new string(charList.ToArray());
}
#endregion

Eric的行政区(省市)下列表控件和标签控件（.net）

a@b.com (bosswin) — Wed, 04 Jul 2007 21:14:31 +0800

省市地区选择在各类项目中都可能要用到, 想要联动又刷新, 想只存地区代码又想显示方便, 还想要开发和部署简便...于是我的 DistrictDropDownList和 DistictLabel 应着全国人民的心声面试了 ^o^;; 这两个控件是本人2005年在公司开发一个网游交易网站时顺便做的. 在2006年试用Atlas时发现WebResource的好

处后对控件做了改良.

DistrictDropDownList 的特点: 客户端使用JS+XML实现省市联动, 在IE6/5, FF2上测试通过.

DistrictDropDownList 和 DistictLabel 共同特点:
1. 主要属性是Code, Code是个Int32的值, 用于存储全国行政区划编号. 这样用1个变量(字段)就能存储省市(县)区3级别的信息.(区级用得少,所以这个版本没包含)
2. 行政区数据信息以XML格式嵌入在控件DLL中, 数据整理自中国国家统计局行政区划代码2006年12月31日版.
2. 在VS里即拖即用,呵呵

演示地址: http://efplatform.net/demo/webcontrols/districtcontrols.aspx
控件下载地址: 200707042123495204.rar

DistrictControls.aspx:

<%@ Page Language="C#" %>

<%@ Register Assembly="EFPlatform.WebControls" Namespace="EFPlatform.WebControls" TagPrefix="efp" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<script runat="server">
    protected void Page_Load(object sender, EventArgs e)
    {
        this.DistrictDropDownList2.Code = 430100;
        this.DistrictDropDownList3.Code = 450500;
        this.DistrictDropDownList4.Code = 210000;
    }

    protected void Button1_Click(object sender, EventArgs e)
    {
        this.DistrictLabel1.Code = this.DistrictDropDownList1.Code;
        this.DistrictLabel2.Code = this.DistrictDropDownList2.Code;
        this.DistrictLabel3.Code = this.DistrictDropDownList3.Code;
        this.DistrictLabel4.Code = this.DistrictDropDownList4.Code;
    }
</script>

<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
    <title>DistrictDropDownList & DistrictLabel Demo</title>
</head>
<body>
    <form id="form1" runat="server">
        <div>
            <efp:DistrictDropDownList ID="DistrictDropDownList1" runat="server" />
            <br />
            <efp:DistrictDropDownList ID="DistrictDropDownList2" runat="server" />
            <br />
            <efp:DistrictDropDownList ID="DistrictDropDownList3" runat="server" />
            <br />
            <efp:DistrictDropDownList ID="DistrictDropDownList4" runat="server" />
            <asp:Button ID="Button1" runat="server" OnClick="Button1_Click" Text="Button" /><br />
            <br />
            <efp:DistrictLabel ID="DistrictLabel1" runat="server">
            </efp:DistrictLabel>
            <br />
            <efp:DistrictLabel ID="DistrictLabel2" runat="server">
            </efp:DistrictLabel>
            <br />
            <efp:DistrictLabel ID="DistrictLabel3" runat="server">
            </efp:DistrictLabel>
            <br />
            <efp:DistrictLabel ID="DistrictLabel4" runat="server">
            </efp:DistrictLabel>
        </div>
    </form>
</body>
</html>

转载：Eric's Bloggy

下载网页中远程图片到本地服务器方法(.net)

a@b.com (bosswin) — Wed, 04 Jul 2007 21:11:41 +0800

在网站内容编辑时, 经常会把别的网站的内容COPY后再PASTE到自己的后台编辑中, 但是其中的图片只是保存的URL, 并未COPY到本地. 下面这个方法能把COPY回来的HTML代码中的图片的URL转换成指定的URL, 并把图片下载到指定的物理路径.

using System;
using System.Collections.Generic;
using System.Text.RegularExpressions;
using System.Net;
using System.IO;

namespace EFPlatform.Helper
{
    public class WebRequestHelper
    {
        #region RequestFileFromHtml
        public static string RequestFileFromHtml(string html, string fileUrl, string filePath, string reservedHost)
        {
            Uri url;
            string fileExt;
            string fileName;
            WebClient c = new WebClient();
            string p = @"((http|https|ftp):(\/\/|\\\\){1}(([A-Za-z0-9_-])+[.]){1,}(net|com|cn|org|cc|tv|[0-9]{1,3})(\S*\/)((\S)+[.]{1}(gif|jpg|png)))";
            Regex r = new Regex(p, RegexOptions.Compiled | RegexOptions.IgnoreCase);
            MatchCollection mc = r.Matches(html);

            if(mc.Count > 0)
            {
                List<Uri> urlList = new List<Uri>();
                int matchIndex = 0;
                bool repeated = false;

                for(int i = 0;i < mc.Count;i++)
                {
                    url = new Uri(mc[i].Value);

                    for(int j = 0;j < urlList.Count;j++)
                    {
                        if(url == urlList[j])
                        {
                            repeated = true;
                            break;
                        }
                    }

                    if(!repeated && (url.Host.ToLower() != reservedHost.ToLower()))
                    {
                        urlList.Add(url);
                        matchIndex++;
                    }
                }

                for(int i = 0;i < urlList.Count;i++)
                {
                    url = urlList[i];
                    fileExt = url.AbsoluteUri.Substring(url.AbsoluteUri.LastIndexOf("."));
                    fileName = string.Format("{0:yyMMddHHmmssff}{1}{2}", DateTime.Now, i, fileExt);

                    try
                    {
                        c.DownloadFile(url, filePath + fileName);
                        html = html.Replace(url.AbsoluteUri, fileUrl + fileName);
                    }
                    catch
                    {
                    }
                }
            }

            return html;
        }
        #endregion
    }

}

转载：Eric's Bloggy

支持GOOGLE，我开通的GOOGLE服务

a@b.com (bosswin) — Wed, 04 Jul 2007 20:22:47 +0800

	AdSense
	Blogger
	Docs and Spreadsheets
	Gmail
	iGoogle
	Page Creator
	Picasa 网络相册
	Reader
	Talk
	本地商户中心
	笔记本
	快讯
	拼音输入法编辑器
	让 Google在说您的语言
	日历
	视频
	网上论坛
	网站管理员工具

Asp.net可以调用RAR实现在线文件压缩与解压缩

a@b.com (bosswin) — Wed, 04 Jul 2007 20:15:14 +0800

如果服务器上安装了RAR程序，那么asp.net可以调用RAR实现文件压缩与解压缩。

  不过要注意的是，由于Web程序不能直接调用客户端的程序（除非用ActiveX，ActiveX几乎被废弃），所以如果要想实现让用户把本地文件用网页解压缩只有把文件上传到服务器上再调用服务器上的RAR压缩，同理要解压缩本地的RAR文件可以把文件上传到服务器解压再拿回来。

  本文讲怎么在服务器端的目录解压缩文件！

  效果图


   查看文章
  asp.net利用RAR实现文件压缩解压缩[转载]2007-06-21 10:39如果服务器上安装了RAR程序，那么asp.net可以调用RAR实现文件压缩与解压缩。

  不过要注意的是，由于Web程序不能直接调用客户端的程序（除非用ActiveX，ActiveX几乎被废弃），所以如果要想实现让用户把本地文件用网页解压缩只有把文件上传到服务器上再调用服务器上的RAR压缩，同理要解压缩本地的RAR文件可以把文件上传到服务器解压再拿回来。

  本文讲怎么在服务器端的目录解压缩文件！

  效果图：


  前台代码：

  ....

  后台代码：

  using System;
  using System.Data;
  using System.Configuration;
  using System.Web;
  using System.Web.Security;
  using System.Web.UI;
  using System.Web.UI.WebControls;
  using System.Web.UI.WebControls.WebParts;
  using System.Web.UI.HtmlControls;
  using System.IO;
  using System.Runtime.InteropServices;
  using Microsoft.Win32;
  using System.Diagnostics;
  public partial class _Default : System.Web.UI.Page
  ...{
   protected void Page_Load(object sender, EventArgs e)
   ...{
   //清清月儿 http://blog.csdn.net/21aspnet/
   }
   protected void Button1_Click(object sender, EventArgs e)
   ...{
   //压缩
   String the_rar;
   RegistryKey the_Reg;
   Object the_Obj;
   String the_Info;
   ProcessStartInfo the_StartInfo;
   Process the_Process;
   try
   ...{
   the_Reg = Registry.ClassesRoot.OpenSubKey("Applications\WinRAR.exe\Shell\Open\Command");
   the_Obj = the_Reg.GetValue("");
   the_rar = the_Obj.ToString();
   the_Reg.Close();
   the_rar = the_rar.Substring(1, the_rar.Length - 7);
   the_Info = " a " + " 1.rar " + " " + "C:\1\1.txt";
   the_StartInfo = new ProcessStartInfo();
   the_StartInfo.FileName = the_rar;
   the_StartInfo.Arguments = the_Info;
   the_StartInfo.WindowStyle = ProcessWindowStyle.Hidden;
   the_StartInfo.WorkingDirectory = "C:\1";//获取或设置要启动的进程的初始目录。
   the_Process = new Process();
   the_Process.StartInfo = the_StartInfo;
   the_Process.Start();
   Response.Write("压缩成功");
   }
   catch (Exception ex)
   ...{
   Response.Write(ex.ToString());
   }
   }
   protected void Button2_Click(object sender, EventArgs e)
   ...{
   //解压缩
   String the_rar;
   RegistryKey the_Reg;
   Object the_Obj;
   String the_Info;
   ProcessStartInfo the_StartInfo;
   Process the_Process;
   try
   ...{
   the_Reg = Registry.ClassesRoot.OpenSubKey("Applications\WinRar.exe\Shell\Open\Command");
   the_Obj = the_Reg.GetValue("");
   the_rar = the_Obj.ToString();
   the_Reg.Close();
   the_rar = the_rar.Substring(1, the_rar.Length - 7);
   the_Info = " X " + " 1.rar " + " " + "C:\1";
   the_StartInfo = new ProcessStartInfo();
   the_StartInfo.FileName = the_rar;
   the_StartInfo.Arguments = the_Info;
   the_StartInfo.WindowStyle = ProcessWindowStyle.Hidden;
   the_Process = new Process();
   the_Process.StartInfo = the_StartInfo;
   the_Process.Start();
   Response.Write("解压缩成功");
   }
   catch (Exception ex)
   ...{
   Response.Write(ex.ToString());
   }
   }
  }


  服务器端目


  客户端变通压缩

ORACLE和SQLServer语法区别归纳

a@b.com (bosswin) — Wed, 04 Jul 2007 19:51:48 +0800

数据类型比较

类型名称
Oracle
SQLServer
比较

字符数据类型 CHAR CHAR 都是固定长度字符资料但oracle里面最大度为2kb，SQLServer里面最大长度为8kb
变长字符数据类型 VARCHAR2 VARCHAR Oracle里面最大长度为4kb，SQLServer里面最大长度为8kb
根据字符集而定的固定长度字符串 NCHAR NCHAR 前者最大长度2kb后者最大长度4kb
根据字符集而定的可变长度字符串 NVARCHAR2 NVARCHAR 二者最大长度都为4kb
日期和时间数据类型 DATE 有Datetime和Smalldatetime两种在oracle里面格式为DMY在SQLSerser里面可以调节，默认的为MDY
数字类型 NUMBER(P,S) NUMERIC[P(,S)] Oracle里面p代表小数点左面的位数，s代表小数点右面的位数。而SQLServer里面p代表小数点左右两面的位数之和，s代表小数点右面的位数。
数字类型 DECIMAL(P,S) DECIMAL[P(,S)] Oracle里面p代表小数点左面的位数，s代表小数点右面的位数。而SQLServer里面p代表小数点左右两面的位数之和，s代表小数点右面的位数。
整数类型 INTEGER INT 同为整数类型，存储大小都为4个字节
浮点数类型 FLOAT FLOAT
实数类型 REAL REAL

ORACLE内部函数大全以及与SQLSERVER的区别：
下面是Oracle支持的字符函数和它们的Microsoft SQL Server等价函数。

函数 Oracle Microsoft SQL　Server
把字符转换为ASCII :ASCII ASCII
字串连接: CONCAT --------------(expression + expression)
把ASCII转换为字符 CHR, CHAR
返回字符串中的开始字符（左起） INSTR ,---------------CHARINDEX
把字符转换为小写 LOWER ---------------------LOWER
把字符转换为大写 UPPER-------------------- UPPER
填充字符串的左边 LPAD --------------------N/A
清除开始的空白 LTRIM--------------------LTRIM
清除尾部的空白 RTRIM --------------------RTRIM
字符串中的起始模式（pattern） INSTR --------------------PATINDEX
多次重复字符串 RPAD --------------------REPLICATE
字符串的语音表示 SOUNDEX --------------------SOUNDEX
重复空格的字串 RPAD --------------------SPACE
从数字数据转换为字符数据 TO_CHAR --------------------STR
子串 SUBSTR --------------------SUBSTRING
替换字符 REPLACE --------------------STUFF
将字串中的每个词首字母大写 INITCAP --------------------N/A
翻译字符串 TRANSLATE --------------------N/A
字符串长度 LENGTH-------------------- DATELENGTH or LEN
列表中最大的字符串 GREATEST-------------------- N/A
列表中最小的字符串 LEAST --------------------N/A
如果为NULL则转换字串 NVL-------------------- ISNULL

　

日期函数

下面是Oracle支持的日期函数和它们的Microsoft SQL Server等价函数。

函数 Oracle --------------------Microsoft SQL　Server
日期相加 (date column +/- value) or ADD_MONTHS --------------------DATEADD

两个日期的差 (date column +/- value) or MONTHS_BETWEEN --------------------DATEDIFF
当前日期和时间 SYSDATE --------------------GETDATE()
一个月的最后一天 LAST_DAY --------------------N/A
时区转换 NEW_TIME --------------------N/A
日期后的第一个周日 NEXT_DAY --------------------N/A
代表日期的字符串 TO_CHAR --------------------DATENAME
代表日期的整数 TO_NUMBER (TO_CHAR)) --------------------DATEPART
日期舍入 ROUND --------------------CONVERT
日期截断 TRUNC --------------------CONVERT
字符串转换为日期 TO_DATE --------------------CONVERT
如果为NULL则转换日期 NVL -------------------- ISNULL

　

转换函数

下面是Oracle支持的转换函数和它们的Microsoft SQL Server等价函数。

函数 Oracle --------------------Microsoft SQL　Server
数字转换为字符 TO_CHAR --------------------CONVERT
字符转换为数字 TO_NUMBER --------------------CONVERT
日期转换为字符 TO_CHAR --------------------CONVERT
字符转换为日期 TO_DATE CONVERT
16进制转换为2进制 HEX_TO_RAW --------------------CONVERT
2进制转换为16进制 RAW_TO_HEX --------------------CONVERT

　

其它行级别的函数

下面是Oracle支持的其它行级别的函数以及它们的Microsoft SQL Server等价函数。

函数 Oracle --------------------Microsoft SQL　Server
返回第一个非空表达式 DECODE -------------------------------------COALESCE
当前序列值 CURRVAL --------------------N/A
下一个序列值 NEXTVAL --------------------N/A

用户登录账号ID数字 UID --------------------SUSER_ID
用户登录名 USER --------------------SUSER_NAME
用户数据库ID数字 UID --------------------USER_ID
用户数据库名 USER --------------------USER_NAME
当前用户 CURRENT_USER -------------------- CURRENT_USER
用户环境(audit trail) USERENV --------------------N/A
在CONNECT BY子句中的级别 LEVEL --------------------N/A

　

合计函数

下面是Oracle支持的合计函数和它们的Microsoft SQL Server等价函数。

函数 Oracle --------------------Microsoft SQL　Server
Average AVG -------------------- AVG
Count COUNT --------------------COUNT
Maximum MAX -------------------- MAX
Minimum MIN --------------------MIN
Standard deviation STDDEV --------------------STDEV or STDEVP
Summation SUM -------------------- SUM
Variance VARIANCE --------------------VAR or VARP
条件测试

Oracle的DECODE语句和Microsoft SQL Server的CASE表达式都执行条件测试。
当test_value中的值和后面的任何表达式匹配的时候，相关的值就返回。如果没有找到任何匹配的值，就返回default_value。
如果没有指定default_value，在没有匹配的时候，DECODE和CASE都返回一个NULL。下表显示了该语句的语法，
同时给出了转换DECODE命令的示例。

Oracle Microsoft SQL　
DECODE (test_value,
expression1, value1
<,expression2, value2] […>
[,default_value]
)
CREATE VIEW STUDENT_ADMIN.STUDENT_GPA
(SSN, GPA)
AS SELECT SSN, ROUND(AVG(DECODE(grade
,'A', 4
,'A+', 4.3
,'A-', 3.7
,'B', 3
,'B+', 3.3
,'B-', 2.7
,'C', 2
,'C+', 2.3
,'C-', 1.7
,'D', 1
,'D+', 1.3
,'D-', 0.7
,0)),2)
FROM STUDENT_ADMIN.GRADE
GROUP BY SSN
CASE input_expression
WHEN when_expression THEN 　　　result_expression

[ELSE else_result_expression]
END
CREATE VIEW STUDENT_ADMIN.STUDENT_GPA
(SSN, GPA)
AS SELECT SSN, ROUND(AVG(CASE grade
WHEN 'A' THEN 4
WHEN 'A+' THEN 4.3
WHEN 'A-' THEN 3.7
WHEN 'B' THEN 3
WHEN 'B+' THEN 3.3
WHEN 'B-' THEN 2.7
WHEN 'C' THEN 2
WHEN 'C+' THEN 2.3
WHEN 'C-' THEN 1.7
WHEN 'D' THEN 1
WHEN 'D+' THEN 1.3
WHEN 'D-' THEN 0.7
ELSE 0
END),2)
FROM STUDENT_ADMIN.GRADE
GROUP BY SSN

　

CASE表达式可以支持用SELECT语句执行布尔测试，这是DECODE命令所不允许的。欲了解关于CASE表达式的详细信息，
请参阅SQL Server联机手册。

　

把值转换为不同的数据类型

Microsoft SQL Server的CONVERT和CAST函数都是多目标转换函数。它们提供了相似的功能，
把一种数据类型的表达式转换为另一种数据类型的表达式，并且支持多种专门数据的格式。

CAST(expression AS data_type)
CONVERT (data type[(length)], expression [, style])
CAST是一个SQL-92标准的函数。这些函数执行同Oracle的TO_CHAR、TO_NUMBER、TO_DATE、HEXTORAW以及RAWTOTEXT函数相同的功能。

这里所指的数据类型是任何表达式将被转换成为的系统数据类型。不能使用用户定义的数据类型。长度参数是可选的，
该参数用于char、varchar、binary以及varbinary数据类型。允许的最大长度是8000。

转换 Oracle Microsoft SQL　Server
字符到数字 TO_NUMBER(?') --------------------CONVERT(numeric, ?')
数字到字符 TO_CHAR(10) --------------------CONVERT(char, 10)
字符到日期 TO_DATE(?-JUL-97')
TO_DATE(?-JUL-1997','dd-mon-yyyy')

TO_DATE('July 4, 1997', 'Month dd, yyyy') --------------------CONVERT(datetime, ?-JUL-97')

CONVERT(datetime, ?-JUL-1997')
CONVERT(datetime, 'July 4, 1997')
日期到字符 TO_CHAR(sysdate)
TO_CHAR(sysdate, 'dd mon yyyy')
TO_CHAR(sysdate, 'mm/dd/yyyy') --------------------CONVERT(char, GETDATE())
CONVERT(char, GETDATE(), 106)
CONVERT(char, GETDATE(), 101)
16进制到2进制 HEXTORAW(?F')-------------------- CONVERT(binary, ?F')
2进制到16进制 RAWTOHEX(binary_column) --------------------CONVERT(char, binary_column)

　

请注意字符串是怎样转换为日期的。在Oracle中，缺省的日期格式模型是“DD-MON-YY”如果你使用任何其它格式，
你必须提供一个合适的日期格式模型。CONVERT函数自动转换标准日期格式，不需要任何格式模型。

从日期转换到字符串时，CONVERT函数的缺省输出是“dd mon yyyy hh:mm:ss:mmm(24h)”。
用一个数字风格代码来格式化输出，使它能输出为其它类型的日期格式模型。欲了解CONVERT函数的详细信息，请参阅SQL Server联机手册。

下表显示了Microsoft SQL Server日期的缺省输出。

Without Century With Century Standard Output
- 0 or 100 (*) Default mon dd yyyy hh:miAM (or PM)
1 101 USA mm/dd/yy
2 102 ANSI yy.mm.dd
3 103 British/French dd/mm/yy
4 104 German dd.mm.yy
5 105 Italian dd-mm-yy
6 106 - dd mon yy
7 107 - mon dd, yy
8 108 - hh:mm:ss
- 9 or 109 (*) Default milliseconds mon dd yyyy hh:mi:ss:mmm (AM or PM)
10 110 USA mm-dd-yy
11 111 Japan yy/mm/dd
12 112 ISO yymmdd
- 13 or 113 (*) Europe default dd mon yyyy hh:mm:ss:mmm(24h)
14 114 - hh:mi:ss:mmm(24h)

　

用户定义函数

Oracle PL/SQL函数可以在Oracle SQL语句中使用。在Microsoft SQL Server中一般可以通过其它方式来实现同样的功能。

在SQL Server中可以用表中给出的查询来代替。

Oracle Microsoft SQL　Server
SELECT SSN, FNAME, LNAME, ) 　　　TUITION_PAID,
　　TUITION_PAID/GET_SUM_
　　MAJOR(MAJOR)
　　AS PERCENT_MAJOR
FROM STUDENT_ADMIN.STUDENT SELECT SSN, FNAME, LNAME, TUITION_PAID, TUITION_PAID/SUM_MAJOR AS PERCENT_MAJOR
FROM STUDENT_ADMIN.STUDENT,
　　(SELECT MAJOR, 　　　　　SUM(TUITION_PAID) SUM_MAJOR
　　FROM STUDENT_ADMIN.STUDENT
　　GROUP BY MAJOR) SUM_STUDENT
WHERE STUDENT.MAJOR = 　　　　　SUM_STUDENT.MAJOR
CREATE OR REPLACE FUNCTION GET_SUM_MAJOR
(INMAJOR VARCHAR2) RETURN NUMBER
AS SUM_PAID NUMBER;
BEGIN
SELECT SUM(TUITION_PAID) INTO 　　　SUM_PAID
FROM STUDENT_ADMIN.STUDENT
WHERE MAJOR = INMAJOR;
RETURN(SUM_PAID);
END GET_SUM_MAJOR; No CREATE FUNCTION syntax is required; use CREATE PROCEDURE syntax.

　

比较操作符

Oracle和Microsoft SQL Server的比较操作符几乎是一样的。

算符 Oracle Microsoft SQL　Server
等于 (=) (=)
大于 (> ) (> )
小于 (< ) (< )
大于或等于 (>=) (>=)
小于或等于 (<=) (<=)
不等于 (!=, <>, ^=) (!=, <>, ^=)
不大于，不小于 N/A !> , !<
在集合中任意成员中 IN IN
不在集合中的任何成员中 NOT IN NOT IN
集合中的任意值 ANY, SOME ANY, SOME
提交集合中的所有值 != ALL, <> ALL, < ALL,
> ALL, <= ALL, >= ALL, !=　SOME, <>　SOME,
<　SOME, >　SOME,
<=　SOME, >=　SOME != ALL, <> ALL, < ALL,
> ALL, <= ALL, >= ALL, !=　SOME, <>　SOME,
<　SOME, >　SOME,
<=　SOME, >=　SOME
像模式（Like pattern） LIKE LIKE
不像模式（Not like pattern） NOT LIKE NOT LIKE
X和y之间的值 BETWEEN x AND y BETWEEN x AND y
不在x和y之间的值 NOT BETWEEN NOT BETWEEN
值存在 EXISTS EXISTS
值不存在 NOT EXISTS NOT EXISTS
值{为|不为}空 IS NULL, IS NOT NULL Same. Also = NULL,
!=　NULL for backward compatibility (not recommended).

　

模式匹配

SQL Server的LIKE关键字提供了有用的通配符搜索功能，这个功能在Oracle中不支持
除了所有的RDBMS都支持的（%）和（_）通配符以外，SQL Server还支持（[ ]）和（[^]）通配符。

（[ ]）字符用来查询在一个范围内的所有单个字符。例如，如果你需要查询包含一个从a到f的字符的数据，
你可以这样写：“LIKE '[a-f]'”或者“LIKE '[abcdef]'”。这些附加的通配符的有效性在下表中给出。

Oracle Microsoft SQL　
SELECT * FROM STUDENT_ADMIN.STUDENT
WHERE LNAME LIKE 'A%'
OR LNAME LIKE 'B%'
OR LNAME LIKE 'C%' SELECT * FROM STUDENT_ADMIN.STUDENT
WHERE LNAME LIKE '[ABC]%'

　

[^]通配符用来标记那些不在特定范围内的字符。例如，如果除了a到f以外的所有字符都是可以接受的，你可以这样书写：
LIKE '[^a - f]'或者LIKE '[^abcdef]'。

欲了解关于LIKE关键字的详细信息，请参阅SQL Server联机手册。

在比较中使用NULL

尽管Microsoft SQL Server传统上支持SQL-92标准的和一些非标准的NULL行为，但是它还是支持Oracle中的NULL的用法。

为了支持分布式查询，SET ANSI_NULLS必须设定为ON。

在进行连接的时候，SQL Server的SQL Server ODBC驱动程序和OLE DB提供者自动把SET ANSI_NULLS设定为ON。
这个设置可以在ODBC数据源、ODBC连接属性、或者是在连接到SQL Server之前在应用程序中设置的OLE DB连接属性中进行配置。
在从DB-Library应用程序中连接时，SET ANSI_NULLS缺省为OFF。

当SET ANSI_DEFAULTS为ON时，SET ANSI_NULLS被允许。

欲了解关于NULL用法的详细信息，请参阅SQL Server联机手册。

　

字串连接

Oracle使用两个管道符号（||）来作为字串连接操作符，SQL Server则使用加号（+）。这个差别要求你在应用程序中做小小的修改。

Oracle Microsoft SQL　
SELECT FNAME||' '||LNAME AS NAME
FROM STUDENT_ADMIN.STUDENT
-----------------------------------------------
SELECT FNAME +' '+ LNAME AS 　　　NAME
FROM STUDENT_ADMIN.STUDENT

　

流控制（Control-of-Flow）语言

流控制语言控制SQL语句执行流，语句块以及存储过程。PL/SQL和Transact-SQL提供了多数相同的结构，但是还是有一些语法差别。

　

关键字

这是两个RDBMS支持的关键字。

语句 Oracle PL/SQL ---------------------Microsoft SQL　Server Transact-SQL

声明变量 DECLARE DECLARE
语句块 BEGIN...END; BEGIN...END
条件处理 IF…THEN,
ELSIF…THEN,
ELSE
ENDIF;
--------------------------------------------------------
IF…[BEGIN…END]
ELSE <condition>
[BEGIN…END]
ELSE IF <condition>
CASE expression
无条件结束 RETURN------------ RETURN
无条件结束当前程序块后面的语句 EXIT BREAK
重新开始一个WHILE循环 N/A CONTINUE
等待指定间隔 N/A (dbms_lock.sleep) WAITFOR
循环控制 WHILE LOOP…END LOOP;
------------
LABEL…GOTO LABEL;
FOR…END LOOP;
LOOP…END LOOP;
WHILE <condition>
BEGIN… END
LABEL…GOTO LABEL

程序注释 /* … */, -- /* … */, --
打印输出 RDBMS_OUTPUT.PUT_LINE PRINT

引发程序错误（Raise program error） RAISE_APPLICATION_ERROR --------------------RAISERROR

执行程序 EXECUTE----------------------EXECUTE
语句终止符 Semicolon ( ------------------N/A

　

声明变量

Transact-SQL和PL/SQL的变量是用DECLARE关键字创建的。Transact-SQL变量用@标记，
并且就像PL/SQL一样，在第一次创建时，用空值初始化。

Oracle Microsoft SQL　
DECLARE
VSSN CHAR(9);
VFNAME VARCHAR2(12);
VLNAME VARCHAR2(20);
VBIRTH_DATE DATE;
VLOAN_AMOUNT NUMBER(12,2);
-----------------------------------------
DECLARE
@VSSN CHAR(9),
@VFNAME VARCHAR2(12),
@VLNAME VARCHAR2(20),
@VBIRTH_DATE DATETIME,
@VLOAN_AMOUNT NUMERIC(12,2)

　

Transact-SQL不支持%TYPE和%ROWTYPE变量数据类型定义。一个Transact-SQL变量不能在DECLARE命令中初始化。
在Microsoft SQL Server数据类型定义中也不能使用Oracle的NOT NULL和CONSTANT关键字。

像Oracle的LONG和LONG RAW数据类型一样。文本和图形数据类型不能被用做变量定义。
此外，Transact-SQL不支持PL/SQL风格的记录和表的定义。

　

给变量赋值

Oracle和Microsoft SQL Server提供了下列方法来为本地变量赋值。

Oracle Microsoft SQL　
Assignment operator (:=) ---------------------SET @local_variable = value
SELECT...INTO syntax for selecting column values from a single row
-------------------------
SELECT @local_variable = expression [FROM…] for assigning a literal value,
an expression involving other local variables, or a column value from a single row

FETCH…INTO syntax------------------------------- FETCH…INTO syntax

　

这里有一些语法示例

Oracle Microsoft SQL　
DECLARE VSSN CHAR(9);
VFNAME VARCHAR2(12);
VLNAME VARCHAR2(20);
BEGIN
VSSN := ?'
SELECT FNAME, LNAME INTO VFNAME, VLNAME FROM STUDENTS WHERE SSN=VSSN;
END;
------------------------------------------------------------------------------
DECLARE @VSSN CHAR(9),
@VFNAME VARCHAR(12),
@VLNAME VARCHAR(20)
SET @VSSN = ?'
SELECT @VFNAME=FNAME, @VLNAME=LNAME FROM STUDENTS WHERE SSN = @VSSN

　

语句块

Oracle PL/SQL和Microsoft SQL Server Transact-SQL都支持用BEGIN…END术语来标记语句块。
Transact-SQL不需要在DECLARE语句后使用一个语句块。
---------------------------------------------------------------------------------
-如果在Microsoft SQL Server
中的IF语句和WHILE循环中有多于一个语句被执行，则需要使用BEGIN…END语句块。

Oracle Microsoft SQL　
DECLARE
DECLARE VARIABLES ...
BEGIN -- THIS IS REQUIRED SYNTAX
PROGRAM_STATEMENTS ...
IF ...THEN
STATEMENT1;
STATEMENT2;
STATEMENTN;
END IF;
WHILE ... LOOP
STATEMENT1;
STATEMENT2;
STATEMENTN;
END LOOP;
END; -- THIS IS REQUIRED SYNTAX DECLARE
DECLARE VARIABLES ...
BEGIN -- THIS IS OPTIONAL SYNTAX
PROGRAM_STATEMENTS ...
IF ...
BEGIN
STATEMENT1
STATEMENT2
STATEMENTN
END
WHILE ...
BEGIN
STATEMENT1
STATEMENT2
STATEMENTN
END
END -- THIS IS REQUIRED SYNTAX

　

条件处理

Microsoft SQL Server Transact-SQL的条件语句包括IF和ELSE，但不包括Oracle PL/SQL中的ELSEIF语句。
可以用嵌套多重IF语句来到达同样的效果。对于广泛的条件测试，用CASE表达式也许更容易和可读一些。

Oracle Microsoft SQL　
DECLARE
VDEGREE_PROGRAM CHAR(1);
VDEGREE_PROGRAM_NAME VARCHAR2(20);
BEGIN
VDEGREE_PROGRAM := 'U'
IF VDEGREE_PROGRAM = 'U' THEN
VDEGREE_PROGRAM_NAME := 'Undergraduate'

ELSIF VDEGREE_PROGRAM = 'M' 　　　　　　　　THEN VDEGREE_PROGRAM_
　　NAME := 'Masters'
ELSIF VDEGREE_PROGRAM = 'P' 　　　　　　　　　　　THEN VDEGREE_PROGRAM_
　　NAME := 'PhD'
ELSE VDEGREE_PROGRAM_
　　NAME := 'Unknown'
END IF;
END;
-----------------------------------------------------
DECLARE
@VDEGREE_PROGRAM CHAR(1),
@VDEGREE_PROGRAM_NAME VARCHAR(20)
SELECT @VDEGREE_PROGRAM = 'U'
SELECT @VDEGREE_PROGRAM_
　　NAME = CASE @VDEGREE_PROGRAM
　　WHEN 'U' THEN 'Undergraduate'
　　WHEN 'M' THEN 'Masters'
　　WHEN 'P' THEN 'PhD'.
　　ELSE 'Unknown'
END

　

重复执行语句（循环）

Oracle PL/SQL提供了无条件的LOOP和FOR LOOP。Transact-SQL则提供了WHILE循环和GOTO语句。

WHILE Boolean_expression
{sql_statement | statement_block}

[BREAK] [CONTINUE]

　

WHILE循环需要测试一个布尔表达式来决定一个或者多个语句的重复执行。
只要给定的表达式结果为真，这个（些）语句就一直重复执行下去。如果有多个语句需要执行，则这些语句必须放在一个BEGIN…END块中。

Oracle Microsoft SQL　
DECLARE
COUNTER NUMBER;
BEGIN
COUNTER := 0
WHILE (COUNTER <5) LOOP
COUNTER := COUNTER + 1;
END LOOP;
END;
------------------------------------------------------
DECLARE
@COUNTER NUMERIC
SELECT@COUNTER = 1
WHILE (@COUNTER <5)
BEGIN
　　SELECT @COUNTER =
　　@COUNTER +1
END

　

语句的执行可以在循环的内部用BREAK和CONTINUE关键字控制。BREAK关键字使WHILE循环无条件的结束，
而CONTINUE关键字使WHILE循环跳过后面的语句重新开始。BREAK关键字同Oracle PL/SQL中的EXIT关键字是等价的。
而在Oracle中没有和CONTINUE等价的关键字

GOTO语句

Oracle和Microsoft SQL Server都有GOTO语句，但是语法不同。GOTO语句使Transact-SQL跳到指定的标号处运行，
在GOTO语句后指定标号之间的任何语句都不会被执行。

Oracle Microsoft SQL　
GOTO label;
<<label name here>> GOTO label

　

PRINT语句

Transact-SQL的PRINT语句执行同PL/SQL的RDBMS_OUTPUT.put_line过程同样的操作。该语句用来打印用户给定的消息。

用PRINT语句打印的消息上限是8,000个字符。定义为char或者varchar数据类型的变量可以嵌入打印语句。
如果使用其它数据类型的变量，则必须使用CONVERT或者CAST函数。本地变量、全局变量可以被打印。可以用单引号或者双引号来封闭文本。

　

从存储过程返回

Microsoft SQL Server和Oracle都有RETURN语句。RETURN使你的程序从查询或者过程中无条件的跳出。RETURN是立即的、
完全的、并且可以用于从过程、批处理或者语句块的任意部分跳出。在REUTRN后面的语句将不会被执行。

Oracle Microsoft SQL　
RETURN expression: RETURN [integer_expression]

引发程序错误（Raising program errors）

Transact-SQL的RAISERROR返回一个用户定义的错误消息，并且设置一个系统标志来记录发生了一个错误。
这个功能同PL/SQL的raise_application_error异常处理器的功能是相似的。

RAISERROR语句允许客户重新取得sysmessages表的一个入口，或者用用户指定的严重性和状态信息动态的建立一条消息。
在被定义后，消息被送回客户端作为系统错误消息。

RAISERROR ({msg_id | msg_str}, severity, state
[, argument1 [, argument2> )

[WITH options]

　

在转换你的PL/SQL程序时，也许用不着使用RAISERROR语句。在下面的示例代码中。
PL/SQL程序使用raise_application_error异常处理器，但是Transact-SQL程序则什么也没用。
包括raise_application_error异常处理器是为了防止PL/SQL返回不明确的未经处理的异常错误消息。
作为代替，当一个不可预见的问题发生的时候，异常处理器总是返回Oracle错误消息。

当一个Transact-SQL失败时，它总是返回一个详细的错误消息给客户程序。因此，除非需要某些特定的错误处理，
一般是不需要RAISERROR语句的。

Oracle Microsoft SQL　
CREATE OR REPLACE FUNCTION
DEPT_ADMIN.DELETE_DEPT
(VDEPT IN VARCHAR2) RETURN NUMBER AS
BEGIN
DELETE FROM DEPT_ADMIN.DEPT
WHERE DEPT = VDEPT;
RETURN(SQL%ROWCOUNT);
EXCEPTION
WHEN OTHER THEN
RAISE_APPLICATION_ERROR
(-20001,SQLERRM);
END DELETE_DEPT;
------------------------------------------------------
/ CREATE PROCEDURE
DEPT_ADMIN.DELETE_DEPT
@VDEPT VARCHAR(4) AS
DELETE FROM DEPT_DB.DBO.DEPT
WHERE DEPT = @VDEPT
RETURN @@ROWCOUNT
GO

　

实现游标

Oracle在使用SELECT语句时总是需要游标，不管从数据库中请求多少行。在Microsoft SQL Server，
SELECT语句并不把在返回客户的行上附加游标作为缺省的结果集合。这是一种返回数据给客户应用程序的有效的方法。

SQL Server为游标函数提供了两种接口。当在Transact-SQL批处理或者存储过程中使用游标的时候，SQL语句可用来声明、
打开、和从游标中抽取，就像定位更新和删除一样。当使用来自DB-Library、ODBC、或者OLEDB程序的游标时，SQL Server
显式的调用内建的服务器函数来更有效的处理游标。

当从Oracle输入一个PL/SQL过程时，首先判断是否需要在Transact-SQL中采用游标来实现同样的功能。如果游标仅仅返回一
组行给客户程序，就使用非游标的SELECT语句来返回缺省的结果集合。如果游标用来从行中一次取得一个数据给本地过程变量，
你就必须在Transact-SQL中使用游标。

　

语法

下表显示了使用游标的语法。

操作 Oracle Microsoft SQL　Server
声明一个游标 CURSOR cursor_name [(cursor_parameter(s))]
IS select_statement;
----------------------------------------------------
DECLARE cursor_name CURSOR
[LOCAL | GLOBAL]
[FORWARD_ONLY | SCROLL]
[STATIC | KEYSET | DYNAMIC | FAST_FORWARD]
[READ_ONLY | SCROLL_LOCKS | OPTIMISTIC]
[TYPE_WARNING]
FOR select_statement
[FOR UPDATE [OF column_name [,…n>]
打开一个游标 OPEN cursor_name [(cursor_parameter(s))];
----------------
OPEN cursor_name
从游标中提取（Fetching） FETCH cursor_name INTO variable(s)
-------------------------------------------------------------------------------------------
FETCH FROM] cursor_name
[INTO @variable(s)]
更新提取行 UPDATE table_name
SET statement(s)…
WHERE CURRENT OF cursor_name; UPDATE table_name
SET statement(s)…
WHERE CURRENT OF cursor_name
删除提取行 DELETE FROM table_name
WHERE CURRENT OF cursor_name; DELETE FROM table_name
WHERE CURRENT OF cursor_name
关闭游标 CLOSE cursor_name; CLOSE cursor_name
清除游标数据结构 N/A DEALLOCATE cursor_name

　

声明一个游标

尽管Transact-SQL DECLARE CURSOR语句不支持游标参数的使用，但它确实支持本地变量。当游标打开的时候，
它就使用这些本地变量的值。Microsoft SQL Server在其DECLARE CURSOR中提供了许多附加的功能。

INSENSITIVE选项用来定义一个创建数据的临时拷贝以被游标使用的游标。游标的所有请求都由这个临时表来应答。因此
对原表的修改不会反映到那些由fetch返回的用于该游标的数据上。这种类型的游标访问的数据是不能被修改的。

应用程序可以请求一个游标类型然后执行一个不被所请求的服务器游标类型支持的Transact-SQL语句。SQL Server返回一个错误，
指出该游标类型被改变了，或者给出一组参数，隐式的转换游标。欲取得一个触发SQL Server 7.0隐式的把游标从一种类型转换为
另一种类型的参数的完整列表，请参阅SQL Server联机手册。

SCROLL选项允许除了前向的抽取以外，向后的、绝对的和相对的数据抽取。一个滚动游标使用一种键集合的游标模型，在该模型中，
任何用户提交的对表的删除和更新都将影响后来的数据抽取。只有在游标没有用INSENSITIVE选项声明时，上面的特性才起作用。

如果选择了READ ONLY选项，对游标中的行的更新就被禁止。该选项将覆盖游标的缺省选项棗允许更新。

UPDATE [OF column_list]语句用来在游标中定义一个可更新的列。如果提供了[OF column_list]，那么仅仅是那些列出的列可以被修改。
如果没有指定任何列。则所有的列都是可以更新的，除非游标被定义为READ ONLY。

重要的是，注意到一个SQL Server游标的名字范围就是连接自己。这和本地变量的名字范围是不同的。
不能声明一个与同一个用户连接上的已有的游标相同名字的游标，除非第一个游标被释放。

　

打开一个游标

Transact-SQL不支持向一个打开的游标传递参数，这一点和PL/SQL是不一样的。当一个Transact-SQL游标被打开以后，
结果集的成员和顺序就固定下来了。其它用户提交的对原表的游标的更新和删除将反映到对所有未加INSENSITIVE选项定义
的游标的数据抽取上。对一个INSENSITIVE游标，将生成一个临时表。

　

抽取数据

Oracle游标只能向前移动棗没有向后或者相对滚动的能力。SQL Server游标可以向前或者向后滚动，具体怎么滚动，
要由下表给出的数据抽取选项来决定。只有在游标是用SCROLL选项声明的前提下，这些选项才能使用。

卷动选项描述
NEXT 如果这是对游标的第一次提取，则返回结果集合的第一行；否则，在结果结合内移动游标到下一行。
NEXT是在结果集合中移动的基本方法。NEXT是缺省的游标提取（fetch）。
PRIOR 返回结果集合的前一行。
FIRST 把游标移动到结果集合的第一行，同时返回第一行。
LAST 把游标移动到结果集合的最后一行，同时返回最后一行。
ABSOLUTE n 返回结果集合的第n行。如果n为负数，则返回倒数第n行
RELATIVE n 返回当前提取行后的第n行，如果n是负数，则返回从游标相对位置起的倒数第n行。

　

Transact-SQL的FETCH语句不需要INTO子句。如果没有指定返回变量，行就自动作为一个单行结果集合返回给客户。但是，
如果你的过程必须把行给客户，一个不带游标的SELECT语句更有效一些。

在每一个FETCH后面，@@FETCH_STATUS函数被更新。这和在PL/SQL中使用CURSOR_NAME%FOUND和CURSOR_NAME%NOTFOUND变量是相似的
。@@FETCH_STATUS函数在每一次成功的数据抽取以后被设定为0。如果数据抽取试图读取一个超过游标末尾的数据，则返回一个为-1的值。
如果请求的行在游标打开以后从表上被删除了，@@FETCH_STATUS函数就返回一个为-2的值。只有游标是用SCROLL选项定义的情况下，
才会返回-2值。在每一次数据抽取之后都必须检查该变量，以确保数据的有效性。

SQL Server不支持Oracle的游标FOR循环语法。

CURRENT OF子句

更新和删除的CURRENT OF子句语法和函数在PL/SQL和Transact-SQL中是一样的。在给定游标中，在当前行上执行定位的UPDATE和DELETE。

　

关闭一个游标

Transact-SQL的CLOSE CURSOR语句关闭游标，但是保留数据结构以备重新打开。PL/SQL 的CLOSE CURSOR语句关闭并且释放所有的数据结构。

Transact-SQL需要用DEALLOCATE CURSOR语句来清除游标数据结构。DEALLOCATE CURSOR语句同CLOSE CURSOR是不一样的，
后者保留数据结构以备重新打开。DEALLOCATE CURSOR释放所有与游标相关的数据结构并且清除游标的定义。

　

游标示例

下面的例子显示了在PL/SQL和Transact-SQL等价的游标语句。

Oracle Microsoft SQL　
-----------------------------------------------------------------------------------------------------------
DECLARE
VSSN CHAR(9);
VFNAME VARCHAR(12);
VLNAME VARCHAR(20);
-----------------------------------------------------------------------------------------------------------
DECLARE
@VSSN CHAR(9),
@VFNAME VARCHAR(12),
@VLNAME VARCHAR(20)
CURSOR CUR1
IS
SELECT SSN, FNAME, LNAME
FROM STUDENT ORDER BY LNAME;

BEGIN
　　OPEN CUR1;
　　FETCH CUR1 INTO VSSN, 　　　　VFNAME, VLNAME;
　　WHILE (CUR1%FOUND) LOOP
　　FETCH CUR1 INTO VSSN, 　　　　VFNAME, VLNAME;
END LOOP;
CLOSE CUR1;
END;
-----------------------------------------------------------------------------------------------------------
DECLARE curl CURSOR FOR
　　SELECT SSN, FNAME, LNAME
　　FROM STUDENT ORDER BY SSN
OPEN CUR1
FETCH NEXT FROM CUR1
　　INTO @VSSN, @VFNAME, @VLNAME
WHILE (@@FETCH_STATUS <> -1)
　　BEGIN
　　FETCH NEXT FROM CUR1 INTO 　　　　　　@VSSN, @VFNAME, @VLNAME
　　END
CLOSE CUR1
DEALLOCATE CUR1

Oracle使用SQL*PLUS,构建完美excel或html输出

a@b.com (bosswin) — Wed, 04 Jul 2007 19:37:55 +0800

通过SQL*PLUS我们可以构建友好的输出，满足多样化用户需求。
本例通过简单示例，介绍通过sql*plus输出xls，html两种格式文件.
首先创建两个脚本:
1.main.sql
用以设置环境，调用具体功能脚本
2.功能脚本-get_tables.sql
为实现具体功能之脚本

示例如下:
1.main.sql脚本:
[oracle@jumper utl_file]$ more main.sql
set linesize 200
set term off verify off feedback off pagesize 999
set markup html on entmap ON spool on preformat off
spool tables.xls
@get_tables.sql
spool off
exit

2.get_tables.sql脚本:
[oracle@jumper utl_file]$ more get_tables.sql
select owner,table_name,tablespace_name,blocks,last_analyzed
from all_tables order by 1,2;

3.执行并获得输出:

[oracle@jumper utl_file]$ sqlplus "/ as sysdba" @main

SQL*Plus: Release 9.2.0.4.0 - Production on Mon Apr 25 10:30:11 2005

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

Connected to:
Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
With the Partitioning option
JServer Release 9.2.0.4.0 - Production

Disconnected from Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
With the Partitioning option
JServer Release 9.2.0.4.0 - Production
[oracle@jumper utl_file]$ ls -l tables.xls
-rw-r--r-- 1 oracle dba 69539 Apr 25 10:30 tables.xls
[oracle@jumper utl_file]$

此处输出为xls文件，通过下图我们可以看到输出效果:

把main.sql脚本中的，spool tables.xls更改为spool tables.htm,我们可以获得htm格式输出，效果如下图:

多线程实现UI异步调用例子(VS 2005)

a@b.com (bosswin) — Sat, 30 Jun 2007 16:23:27 +0800

这个例子是以前自己用VS 2005写的多线程实现UI异步调用，实现多线程向一个listBox控件添加数据的简单示例（拿出来献丑了，呵呵）。

一、申明一个委托类型：
delegate void myMessage(string message);
二、具体实现方法：

CODE:

private void ListAdd(string msg)
      {
         lock (this.listBox1)
         {
            this.listBox1.Items.Add(msg);
            this.listBox1.SetSelected(listBox1.Items.Count - 1, true);
         }
      }

      private void ListAdds(string msg)
      {
         Invoke(new myMessage(ListAdd), msg);
      }

三、自定义线程对象：

CODE:

using System;
using System.Collections.Generic;
using System.Text;
using System.Threading;
using System.IO;
using System.Windows.Forms;
using System.Diagnostics;

namespace Thread_delegate
{
class Worker
{
      private string _num;
      public Thread myThread;
      public myMessage message;
      public Searcher(string num)
      {
         _num = num;
         myThread = new Thread(DoWork);
      }
      public void Start()
      {

            myThread.Start();
      }
      private void DoWork()
      {
         while(true){
            message("线程" + _Dir);
            Thread.Sleep(1000);
         }
      }
}
}

四、调用线程对象：

CODE:

private Worker[] myWorker = new Worker[5];
      private int num=3;
      public Form1()
      {
         InitializeComponent();
         for (int i = 0; i < num; i++)
         {
            myWorker[i] = new Worker(i.ToString());
            myWorker[i].message += new myMessage(ListAdds);
         }
      }

DEMO下载：多线程与委托.rar

代码小猪

Knowledge Base Home

Google Summer of Code

Google Summer of Code™

Mentoring Organizations Participating in Google Summer of Code 2007

Questions?

Query API Developer Guide

Query API Developer Guide

Contents

Getting Started

Registering With the Query API

Native Plug-in Registration

interface IGoogleDesktopRegisterQueryPlugin: IDispatch

Script Plug-in Registration

Query Objects

Query Methods for Native Plug-Ins

interface IGoogleDesktopQueryAPI: IDispatch

Query Methods for Script Plug-Ins

QueryEx Query Objects

QueryEx for Native Plug-Ins

interface IGoogleDesktopQuery: IDispatch

QueryEx for Script Plug-Ins

Result Objects

Result Objects for Native Plug-Ins

interface IGoogleDesktopQueryResultSet: IDispatch

Result Objects for Script Plug-Ins

Individual Search Result Objects

Individual Search Result Items for Native Plug-ins

interface IGoogleDesktopQueryResultItem: IDispatch

Individual Search Result Items for Script Plug-ins

Item Versions

Item Versions in Native Plug-ins

interface IGoogleDesktopDocumentVersions: IDispatch

Item Versions in Script Plug-ins

HTTP/XML-Based Query API

Getting Started

Requesting a Desktop Search

Getting the Stored Query URL

Windows

Mac OS X

Desktop Search Results

.Net反编译工具Reflector

.NET模板引擎 (代码生成器 静态页生成 生成HTML 模板)

Eric 的随机文件名 生成方法

Eric的行政区(省市)下列表控件和标签控件（.net）

下载网页中远程图片到本地服务器方法(.net)

支持GOOGLE，我开通的GOOGLE服务

Asp.net可以调用RAR实现在线文件压缩与解压缩

ORACLE和SQLServer语法区别归纳

Oracle使用SQL*PLUS,构建完美excel或html输出

多线程实现UI异步调用例子(VS 2005)

`interface IGoogleDesktopRegisterQueryPlugin: IDispatch`

`interface IGoogleDesktopQueryAPI: IDispatch`

`interface IGoogleDesktopQuery: IDispatch`

`interface IGoogleDesktopQueryResultSet: IDispatch`

`interface IGoogleDesktopQueryResultItem: IDispatch`

`interface IGoogleDesktopDocumentVersions: IDispatch`

.NET模板引擎 (代码生成器静态页生成生成HTML 模板)

Eric 的随机文件名生成方法