Below is the list of changes that have just been committed into a local
6.0 repository of eric. When eric does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://dev.mysql.com/doc/mysql/en/installing-source-tree.html
ChangeSet@stripped, 2007-10-20 21:49:01+02:00, eherman@stripped +1 -0
updated the presentation slightly.
Docs/UDF_NG_PRESENTATION@stripped, 2007-10-20 21:48:58+02:00, eherman@stripped +14 -3
updated the presentation slightly.
diff -Nrup a/Docs/UDF_NG_PRESENTATION b/Docs/UDF_NG_PRESENTATION
--- a/Docs/UDF_NG_PRESENTATION 2007-10-19 21:25:13 +02:00
+++ b/Docs/UDF_NG_PRESENTATION 2007-10-20 21:48:58 +02:00
@@ -40,8 +40,18 @@ can be written in the same language as y
[Either of us may speak to this point:]
Start with an example where we imagine a Java application that uses a mysqld
backend. Describe that this application has a very domain specific way of
-treating some of its string data. [is "pig latin" or "string reverse" a better
-example?] -- There are number of solutions:
+treating some of its string data. Imagine a very domain specific sorting need
+... as a trivial example, let's say we need to page through our accounts table
+using a Pig Latin sort. Ideally, we'd like to be able to prepare a statement
+like this:
+
+ SELECT name, email
+ FROM accounts
+ WHERE ?
+ ORDER BY pig_latin(name)
+ LIMIT ?,?
+
+But what are our options?
1) Ignore it: pull back the entrie result set, and do all the work in the
application. (bad for obvious reasons)
2) Use the existing UDF/SP framework
@@ -168,5 +178,6 @@ He has joined MySQL in 2003 as a Senior
Eric Herman - implemented proof-of-concept "judf" for using MySQL existing
user defined functions interface for loading and executing java functions, and
-developer of database backed java applications
+developer of database backed java applications. He joined MySQL in 2004 and
+works on the Enterprise Tools team.
| Thread |
|---|
| • bk commit into 6.0 tree (eherman:1.2639) | eherman | 23 Oct |