Oracle v. Google Assigned to Judge William Alsup, the Apple v. Psystar Judge

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Oracle v. Google Assigned to Judge William Alsup, the Apple v. Psystar Judge
# 1  
Old 09-23-2010
Oracle v. Google Assigned to Judge William Alsup, the Apple v. Psystar Judge

Google has appeared in the Oracle v. Google litigation and they have extra time to file an answer to Oracle's complaint. Meanwhile, they've added some more lawyers to the team and informed the court they decline to have the case handled by a magistrate judge, so it's been assigned to the Hon. William Alsup. What are the odds? That's the same judge who presided over the Apple v. Psystar case.
One thing we saw with him in covering that case: he doesn't much like shenanigans by parties or their lawyers. He's already issued instructions [PDF] to the parties on what he expects of them in discovery and in general, and you can see that he didn't just fall off a turnip truck.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

how to judge wether a url is valid or not using awk

rt 3ks:confused: (6 Replies)
Discussion started by: rainboisterous
6 Replies

2. Programming

to judge a file

HI all I am a newer learning C that I want to write a code to judge a file whether exist or not And rename it. Maybe someone can tell me C whether has function to do it thx (2 Replies)
Discussion started by: jeter
2 Replies
Login or Register to Ask a Question
Session::Store::Oracle(3)				User Contributed Perl Documentation				 Session::Store::Oracle(3)

NAME
Apache::Session::Store::Oracle - Store persistent data in a Oracle database SYNOPSIS
use Apache::Session::Store::Oracle; my $store = new Apache::Session::Store::Oracle; $store->insert($ref); $store->update($ref); $store->materialize($ref); $store->remove($ref); DESCRIPTION
Apache::Session::Store::Oracle fulfills the storage interface of Apache::Session. Session data is stored in a Oracle database. SCHEMA
To use this module, you will need at least these columns in a table called 'sessions': id varchar2(32) # or however long your session IDs are. a_session long To create this schema, you can execute this command using the sqlplus program: CREATE TABLE sessions ( id varchar2(32) not null primary key, a_session long ); If you use some other command, ensure that there is a unique index on the table's id column. CONFIGURATION
The module must know what datasource, username, and password to use when connecting to the database. These values can be set using the options hash (see Apache::Session documentation). The options are DataSource, UserName, and Password. Example: tie %hash, 'Apache::Session::Oracle', $id, { DataSource => 'dbi:Oracle:database', UserName => 'database_user', Password => 'K00l' }; Instead, you may pass in an already-opened DBI handle to your database. tie %hash, 'Apache::Session::Oracle', $id, { Handle => $dbh }; The last option is LongReadLen, which specifies the maximum size of the session object. If not supplied, the default maximum size is 8 KB. AUTHOR
This modules was written by Jeffrey William Baker <jwbaker@acm.org> A fix for the commit policy was contributed by Michael Schout <mschout@gkg.net> SEE ALSO
Apache::Session, Apache::Session::Store::DBI perl v5.12.1 2007-09-28 Session::Store::Oracle(3)