I'm a 33-year-old freelance webdeveloper and photographer living near The Hague, The Netherlands.
This is my personal weblog, where I often post selections of my favourite photos.
Sometimes I make art with code.
Mail me at milovermeulen at gmail dot com.
Ooh, I like the effect with the monkey on http://milov.nl/cat/animals *if* the browser is maximized at 1024x768. The wall his legs are dangling over seems to crush the picture below.
Jan!, that's awesome! I've been planning to generate a view like that with php for ages, never got round to it. Now I see that it would look very cool indeed. For convenience I've added your bookmarklet as a draggable link to the entrytext above.
Hoi Milo,
Kun je het contrast, resp. de gamma-factor van de foto nog wat aanpassen? Ik zie nu alleen een silhouet van het station, en zie niet goed de interessante fietsen-samenscholing. Of is dit contrast de artistieke opzet?
Don't know why, but some photos just work so much better when black-and-white. This is one of them. I just "see" more in this than in the colour version.
1. posted by Kethinov at 04:56 on
December 23, 2004
Thanks for the link up. It's slow going. I do plan to include more than just TNG reviews. I'll be going by release date omitting the movies (until Generations) and TOS.
Once I hit TNG season 6, I'll begin DS9 reviews as well, as DS9 started season 1 in TNG's season 6.
2. posted by Bigougit at 05:15 on
January 03, 2007
Projectj.net is now an add website that uses jrock bands to hide the fact that its nothing but adds.
You should take down your link so noone gets roped into massive popups or something.
http://project-j.org is the new address for Project J. Someone grabed my domain when it expired and replaced it with these seemingly relevant ads. Everything is available again at project-j.org
This is so strange and bulky. Like something falling from the sky. I love images that make me wonder, where I almost seem to know what it might be, but the recognition fails and misfires, leaving me in mystery and consternation.
ilike won bin,coz he's so cute n i adore korean film like the hotelier, love story in harvard, full house, winter sonata...bae yong jun is cool....i ..love kim tae he n kim rae won
i want to know information about scholarship to school in south korea...coz korea is one of stronger country in Asia n in the world about the nuclear in north korea...it's so dangerous n if u want to know maybe can make the radiation so watch out.........
Here's a nice, compact, easily clickable view of all 236 quicklinks I ever posted (well, all those since May 2004 anyway, which is when I first started grouping them in their own category).
1. posted by Calm_Pear at 23:22 on
December 08, 2004
SET? thats odd... thats a syntax for an UPDATE... It looks like the guys that are working on MYSQL are becoming more like the microsoft people... any idiot should be able to get some data in the database... not good if you'd ask me
why would you think there is anything wrong with that syntax? This makes it much easier than INSERT INTO VALUES, you don't have to count through each of the values fields to find the value that corresponds to the column, this is a great syntax addon.
8. posted by the hatter at 12:36 on
October 28, 2006
We think there's something wrong with this syntax because it is not part of the SQL specifications, as far as I can see. Not that language extensions by themself are a bad thing, but one that replicates an extraordinarily well known method seems silly. Most people use DBs through a language API, if you want to write nicer queries, there's nothing to stop someone adding this sort of extension to their API.
this is in the 'INSERT' doc on mysql offical pages...
this makes it easyer to do loops on the values and their names... ie. php's foreach(), instead of having 2, the names and values seperate, you can now just do 1 loop seeing that the names and values are right next to each other.
this also makes reading and matching the things a hell lot easyer...
you can now tell if you have 6 names but only 5 values, without counting them all :P
10. posted by Takashi.pl at 14:21 on
July 25, 2007
well, this syntax sure makes thigs easier to code in php etc., and that's a big plus...
but I think you can only use this syntax if you are sure that your code won't be used under diffrent db engine
This is a nice way and works well. 1 word of caution though, if you want your code to be more universal I would stick to the INSERT INTO and VALUES since this will work both in access and SQL. Obviously most of you will be like, WHAT! ACCESS?!?!?!? But for my company our development is in access then we port that to SQL, I know... I dont have the power to make them change, but for any visitors that might be in the same boat, just a good thing to remember.
I have to second JVirus on that. I've just been working on porting some MySQL code to use PostgreSQL, which uses the standard syntax. Using syntax specific to one vendor, when there's a standard that achieves the same thing, is not the smartest move.
Also worth noting while I'm dealing with the pain of porting from one DB to another - don't use MySQL's double quotes for strings - not standard, not portable, not good :(
14. posted by gmail.com,tushar.iuselinux,Tushar Mahajan at 08:14 on
September 17, 2009
Using first option we can insert multiple values LIKE
I just started a new job and ran across this in some code today. I've worked with various dbs over the year but never knew of this syntax. It disgusts me since it's not the standard. However, I will say it seems more logical and nicer looking. I'm still not going to adopt it though.
this patern is very good for using OOps
i like this patertn to using this commands insert into table_name set fieldname=value it is a very good type of this
While I agree about standards, I think that if the query will only be used on MySQL, it is perfectly valid. If you are working on a larger project that might be used with various DBs, you should probably be using some kind of DB abstraction layer that takes care of the details for you.
18. posted by sousgarden at 14:06 on
October 12, 2010
This function is crap.
I have code now (not my) which have to work on mysql 5.1, previous DB was 5.0.
If I try now to insert with an auto-increment primary I get an error. Cause the coder was sooo an idiot and make following insert:
INSERT INTO table SET COL_PRIMARY="", COL_TEXT1="blabla";
And the primary column now try to insert NULL what not work and have NOT to WORK!!!!!
That this shit work before was not good.
19. posted by justDroppingBy at 05:38 on
November 22, 2010
@sousgarden: this code is a good way of inserting values in a table; faster and easier.
My question is, why would you insert a value to an AI column? AND whether you use the old code or this to insert a NULL value in an AI column it'll still give you errors.
sousgarden:
The first thing you need to learn ; be polite!
The second ; In both syntax you'd better stop setting any Autoincrement field. Your table's index field's auto increment parameters might be wrong i guess. And about the insert into thing; useful for small queries if it's not slower (is it?).
Calm_Pear says, "any idiot should be able to get some data in the database... not good if you'd ask me"
Well, this is the quintessence of the 'feature enhancements are a threat to my job' mentality.
How about you imagine how much easier it will be to dynamically construct and validate INSERT statements within a Database Abstraction Layer that makes your skills even *more* valuable?
Furthermore... I think this syntax *should* be added to standard SQL, along with "INSERT... ON DUPLICATE KEY UPDATE" these are natural and intrinsic *database* tasks, not API tasks... why the 1992 folks didn't see that clarity and elegance of making the UPDATE syntax and INSERT syntax as parallel as possible, *then* adding the standard syntax as a 'power load' alternative is beyond me.
I respect those that refuse to use any proprietary SQL constructs for portability -- and those that choose to use proprietary constructs have an added documentation obligation to identify where those constructs were used for eventual portablity. But for me I would rather endure one-time, upfront documentation task and leverage the power of the proprietary construct continually.
I also believe that *using* the best alternative sql constructs make it *more* likely that there will be a 'critical mass' behind eventally including them in the standard.
Further, 'disgust' with MySQL? MySQL is not the only vendor deploying alternative SQL constructs -- I think Oracle has an equivalent to "INSERT... ON DUPLICATE KEY UPDATE" that is proprietary, and MS SQL has a great number of these -- this is further muddied by the fact that by co-opting in the popular consciousness that "SQL" is not a Language, but a product of Microsoft Corporation. (Admittely, it would seem Microsoft has done the best job with Cross-Tabs, but I dunno much there?...)
Not a Flame against MS SQL or any other, so don't scorch me back :-) -- just pointing out that whatever tool you use, you need to be aware of what code will be universally portable and what will not.
Happy coding...
23. posted by mctsoft.net,matt,Matt at 10:06 on
July 20, 2011
I must be an idiot, I like it, I like anything that makes life easier, I guess if I was smart I would write all my code in assembly instead of PHP and MySQL
24. posted by Ivan Ivkovich at 14:09 on
September 15, 2011
The reason this was implemented :
After altering the table, you have to edit every single webpage containing query with 'INSERT INTO table VALUES' because you have to add '' if there is a new collumn in every query.
If you have SET to a specific column, you don't have to worry about the columns you won't fill with data.
One difference: I'm using http://php.net/fsockopen instead of fopen. Also, I don't do a second request to see if the favicon url returns a valid response.
I added this photoblog to my list of More High Fidelity Home Page Examples which will be given to readers of Usability Interface online newsletter out of Brussels, when they request it in response to my recently published article.
Hope this gives you a little added exposure and increased traffic.
My 2005 date on art specimen at my site is a work around to make that piece appear at top of pile no matter what else I add to my blog.
favourite own photos of 2004
1. posted by Jan! at 11:00 on January 06, 2005
javascript:var maxWidth = maxHeight = 150, html = '<body bgcolor="black">', img = document.getElementsByTagName('div')[1].getElementsByTagName('img'); for (var i = 0; i < img.length; i++) { html += '<img style="max-width: ' + maxWidth + 'px; max-height: ' + maxHeight + 'px;" src="' + img[i].src + '" alt="' + img[i].alt + '" />'; } html += ' </body>'; var d = window.open('', '').document; d.write(html); void d.close();
Yessir, that's me being ever so productive again.
2. posted by Jan! at 11:05 on January 06, 2005
3. posted by Milo at 11:13 on January 06, 2005