The PHP Vikinger is a community-driven PHP event that will be held in Skien, Norway on June 24th an 25th. Like the famous Foo Camp and Bar Camp, PHP Vikinger is driven by its attendees. The people who come choose and present the sessions at the event.

Attendance is by a mix of invitation and registration. 50 …

The PHP Vikinger is a community-driven PHP event that will be held in Skien, Norway on June 24th an 25th. Like the famous Foo Camp and Bar Camp, PHP Vikinger is driven by its attendees. The people who come choose and present the sessions at the event.

Attendance is by a mix of invitation and registration. 50 invitations have been sent to various PEAR and PHP contributors and 50 spots are open for people who register. Additionally, the invitees have been asked to nominate another 50 people who should be invited to the event.

The event is …

The PHP Vikinger is a community-driven PHP event that will be held in Skien, Norway from June 24th to 25th. Like the famous Foo Camp and Bar Camp, PHP Vikinger is driven by its attendees. The people who come choose and present the sessions at the event.

Attendance is by a mix of invitation and registration. 50 invitations have been sent to various PEAR and PHP contributors and 50 spots are open for people who register. Additionally, the invitees have been asked to nominate another 50 people who should be invited to the event.

The event is meant to be as affordable as possible; registration is only 20 Euros, and simple food and a place to sleep are …

I just sent out the invitations for the PHP Vikinger event. My method for choosing who to invite was pretty simple - I chose people listed in the the PHP and PEAR credits who I had written personal email to in the last few years.

Nepotistic? “Nay”, say I, “Nepotastic!” I know that the people I invited are cool, which will mean a good event for people who register. Also, as we have registrations, it won’t be too elitist or exclusive.

If you are curious, read on for the entire invitation (minus the list of attendees.)

NOTE: If you didn’t get an invitation email, then hold tight - you will still be able to register in a week or so.

Aloha $person,

This is an invitation to the PHP Vikinger - read on for details.

WHAT IS IT?
“”"”"”"”"”"
The PHP Vikinger is a community-driven PHP event that will be …

Now that I am a happy user of PHP5 and MySQL5 and using that for writing a new application, which fortunately involves using the newest technologies, I am finally able to solve one of the biggest issues I always had had with DB-driven applications: foreign key contraints.

Constraints and transactions
I am using InnoDB (I know those contraints had been possible before MySQL5) for that and the first time I am also using the foreign key constraints InnoDB provides. And it does make me happier :-). I don’t have to take care of updating and deleting all the referenced table rows myself, the DB’s storage engine does that for me, as I always had wanted it.

I had started out using MyISAM tables and triggers, but when I realized that I am programming the application using transactions I had to switch to InnoDB …

We all deal with queries that return more rows than what our screen will let us view, wouldn’t it be nice to be able paginate the results ?
Rather than having to scroll back, and scan the rows, you can use the built in pager. I didn’t know about this, until Will from freenode mentioned it in #mysql. Long story short..

mysql> \P less
mysql> PAGER set to less
mysql> select foo,bar from table

The format is much more readable than usual. Some of you may have already known about this, but I didn’t. So I hope it’s helpful.

Tags: mysql, tips_and_tricks

We all deal with queries that return more rows than what our screen will let us view, wouldn't it be nice to be able paginate the results ?
Rather than having to scroll back, and scan the rows, you can use the built in pager. I didn't know about this, until Will from freenode mentioned it in #mysql. Long story short..


mysql> \P less
mysql> PAGER set to 'less'
mysql> select foo,bar from table\G



The format is much more readable than usual. Some of you may have already known about this, but I didn't. So I hope it's helpful.

Kursziele:

Der Workshop macht Sie fit für die Entwicklung von Webapplikationen auf Basis von PHP 5 und IBM DB2. Die Themen Objektorientierung, PDO und ibm_db2 stehen dabei im Vordergrund. Dabei zeigt der Kurs die neuen Möglichkeiten, die durch die ibm_db2 Extension realisierbar sind.
Zum Abschluss wird im Team eine kleine Anwendung auf Basis von PHP 5 und IBM DB2 entwickelt.

Inhalt:

• Sprachreferenz PHP
• Objektorientiertes Programmieren mit PHP 5
• Sichtbarkeit, Exceptions und Iteratoren
• PHP und Datenbanken
• Vorstellung von SQLIte, MySQLi und PDO
• IBM DB2 und PHP
• Funktionsumfang der ibm_db2 Extension
• Entwicklung einer eigenen Anwendung

Start: 30.05.2006 10.00 Uhr
Ende: 31.05.2006 17.00 Uhr
Dauer: 2 Tage
Ort: IBM Düsseldorf - PSC - Raum Lippe
…

A few days ago, I tried to use an opensource mailing list manager program, it had great reviews and seemed to have the features I wanted. So, I tried it out, to my dismay just the installer alone had issues, when I went to the install page (thank you for making one in the first place), I was presented with lots and lots of PHP on screen..obviously, I was confused, this is PHPcult.com after all, and the server is configured to parse .php, .php3, .inc. So, I had to do some digging as to what was causing the problem.. the programmers used short open tags for PHP. So, I thought, I need to make a list of things that people do, that may come and bite them later on down the road. Here goes:

• Register Globals : This has been discussed more than it should be, it’s a simple concept, just take it from the more experienced programmers, this is bad.
• Short Open Tags: This is when you use …

I'll be giving my "usual" PDO talk at both MySQL Users Conference 2006 and OSCON 2006 (the MySQLUC version of the talk will have a MySQL focus).

If you're interested in PDO and haven't had the opportunity to see me give this talk yet, please consider trying to get to one of these conferences. My talk covers the design decisions behind PDO, suggests some best practices for using it, highlights portability concerns (particularly because PHP programmers have been "dummied down" by the older mysql client library API) and more.

As usual, I'm always open for questions during the talk (I'm there for your benefit after all) and I try to make myself more generally available during the conference, so if you want to ask me questions, or even just have a chat, then feel free to approach me.