DISQUS

Wow! That is seriously bad news. What a total bummer.

Hi.

This is going to ramble and probably be flame-bait so I appologise in advance. :)

First, we felt liberated from client-server by the net, but were lacking functionality.

Next, we tried using Java applets or OCXs to get that client-server feel, but people objected to having to install a specific JRE version and download whole applets, or being limited to a single vendors browser.

Now we use DHTML and AJAX to try and recreate client-server experience, but this has many browser compatibility issues and involves downloading large Javascript libraries, so it's not disimilar to the problems with applets.

The immediate future looks like a rise in client-side apps built on proprietry frameworks, accessing data from web services.

Let's take the case of email. If I have a client side app accessing my gmail account as a web service, this is no different to having a PC IMAP client accessing my server based IMAP email account. All the data is still centralized on my server, not downloaded to my PC like POP, although I can download it if I know I need it offline. So what have we invented here?

What the net has always lacked is a standard framework for interactive applications. We shouldn't be relying on one million and one DHTML or AJAX toolkits. This functionality should either be part of the browser, or part of a standard "web-app" component. That way, people can concentrate on writing useful apps, not worrying about implementation issues caused by the limitations of the platform.

I have a lot of respect for all the people doing amazing things with DHTML and AJAX, but it really is trying to fix the problem with a band aid. At some point in the future we will look back at this and laugh at how ridiculous it all was.

I know it's been said before and it's all a bit idealistic, but the browser in its current form is not the tool for complex interactive applications. :)

Cheers

Tim...

Hi.

You could do some of your basic testing without installign different browsers if you use this:

http://browsershots.org/

Cheers

Tim...

Hi.

I think it's great how Mix has given customers another way to voice their opinions.

What worries me is most folks don't get involved, so there is a danger that passionate minority opinions are affecting the road map for the majority.

I guess this is just like politics, so if people don't like it they've got to get involved. :)

Cheers

Tim...

PS. This comment is not aimed at Apple, so don't flame me. :)

Over time some networks will die, some will remain popular, some will be integrated into other networks. While a network adds value it will remain. When it ceases to add value people will cease to visit and it will die.

In some ways I would like to see integration, but on the other hand I like the separation. I don't want the bloat of Facebook if all I want to do is twitter.

The biggest problem with integration for me is the lack of fine control over what gets seen. I don't want my friends mixing up with my workmates or my Oracle network. Each network of people would be innundated with information that is meaningless to them.

Instead, the big social networks should allow a finer grouping control of connections, so you can keep your personal life separate from your work life etc.

Until this sort of control is introduced, I'm happy to use Facebook for friends, LinkedIn for work and Mix for Oracle etc.

Cheers

Tim...

Hi.

This is a good place to start:

http://en.wikipedia.org/wiki/Web_2

It mentions a whole bunch of stuff including:

social-networking sites (Myspace & Facebook etc.)
social bookmarking (Digg, del.icio.us, StumbleUpon)
podcasts
wikis (Wikipedia :) )
blogs
folksonomies (I guess this is social-tagging/bookmarking)
RSS (syndication)
Mashups
etc.

Cheers

Tim...

Don't blame me. I was Dan Norris...

Anyway, you were a member of Twitter before me, so you definitely can't put that one on me. :)

Cheers

Tim...

Andy:

I like your blog, that's why I include it in my aggregator. If other people don't like it they can move along. :)

Don't let it get you down. I'm sure you won't, but I want to say it anyway.

Cheers

Tim...

No news is bad news. You can probably get on "Celebrity Big Brother" or "Celebrity Love Island" on the back of this. ;)

Cheers

Tim...

That's so unfair. Sigue Sigue Sputnik were fun. :)

Cheers

Tim...

I like it. Keep tagging.

Cheers

Tim...

RE: 6

Yet... :)

Cheers

Tim...

I got tagged by Chris Muir. I've been a good boy and tagged 8 others. Do I get a gold star?

CHeers

Tim...

I was really looking forward to meeting you at the Bloggers do. I asked a few people if they had seen you, then Doug told me your blog post was a rather dry dig at your employer. Bummer!

As two of the most off-topic Oracle bloggers in the current blogsphere, I think it is our destiny to meet! :)

Cheers

Tim...

Wow. High praise indeed. The cheque's in the mail. :)

Cheers

Tim...

Mark really is a bad influence... :)

Hi.

The instance is still screwed using the catalog.sql approach. Looks like doing anything with the standard package is a bad idea.

I guess we will have to wait and see what Oracle say.

Cheers

Tim...

Whoops. Should have used catalog.sql, not catproc.sql! I'm trying again now. :)

Cheers

Tim...

Hi.

I would suggest anything that requires the standard package to be recompiled is probably cause for a rerun of the catproc.sql script.

I tried the compile-only method and it invalidated over 7000 objects, most of which wouldn't recompile when I ran the utlrp.sql script.

The following seemed to work fine:

CONN / AS SYSDBA
ALTER SESSION SET plscope_settings='IDENTIFIERS:ALL';
@?/rdbms/admin/catproc.sql
@?/rdbms/admin/utlrp.sql

At the end of this I had no invalid objects and the DB seemed fine. Even so, I'm switching back to a snapshot just in case. :)

Cheers

Tim...

Hi.

It works with no problems without doing the addition compile of the standard package:

http://www.oracle-base.com/articles/11g/PlsqlNewFeaturesAndEnhancements_11gR1.php#plscope

Cheers

Tim...

I hope this pus that whole issue to bed. :)

Cheers

Tim...

I love CenterParcs. I've been the last few years with my Brother and his kids. It's a right good laugh. I admit, if there are no kids present it would probably lose its appeal. :)

Cheers

Tim...

LOL :)

Regarding Documentation:

Yes, the bug I raised was against the documentation. It originally quoted the old 2000 byte limit.

I've not checked recently, but the old 10.1 documentation was left with the incorrect value.

Cheers

Tim...

The limit is actually >4000 in 10g. I know because I spotted it and raised it as a bug (4330467) on metalink, only to be told it was a "feature" of 10g.

Cheers

Tim...