| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
Comments:
<0> my db :), good example, lemme check that.
<1> rmah, I don't think this apache server forks the perl processes
<2> additionally, your RDBMS can possibly cache prepared statements with placeholders
<2> it cannot do that, otherwise
<3> MrBIOS: it better not since you said it was mod_perl
<1> it is
<1> it's strange that it's not writing any log files, everything looks kosher
<3> check that the dirs are there
<1> I made them, perms are correct
<3> and that they're writable by whatever the process is runnnig as
<3> etc
<3> then I don't know
<0> thrig, maybe I am too lammer, but the placeholder seems to be the non secure aspect, right?
<3> guisfo, placeholders good
<0> thanks tag for your point.
<3> stuff like: $db->do("INSERT INTO t SET i = $i") BAD BAD BAD
<2> stored procedures are better
<2> and stored procedures with place holders, are very good good good.
<3> tag: only if you're one of them dba freaks
<4> gnargh. could antarctica please just piss off? :/
<0> :)
<2> rmah: or you're one of those people who thinks putting HTML and SQL and other languages in my Perl, Java, Pike, or whatever programming language source code, is a bad idea
<2> which...it is.
<5> mmm, (stored procedures + placeholders)++
<3> tag: I have no problem with SQL
<0> thanks for the support guys :)
<3> I hate stored proces because there is no structure for managing them (namespaces, packages, etc.)
<3> I also can't p*** objects from my apps to/from them
<3> etc, etc, etc
<3> I'd rather have a bit of SQL in my app code
<3> but that's me... you may feel differently
<2> rmah: that's because you either have yet to or aren't smart enough to realize that putting SQL in string literals in your source code is in fact no different than putting HTML in your source code, and you also have yet to realize that a relational database is in and of itself a seperate application and treating it as such promotes stability, portability, maintainability, and FLEXIBILITY
<2> all of the important ibilities
<5> + scalability
<3> tag: I disagree
<3> tag, in my experience, stored proces lead to more headaches
<3> but that's my experiences... yours may differ
<2> rmah: that's because you obviously don't know enough about the world, there is no reason to disagree with that, other than maybe you don't know PL/SQL, or quite possibly don't like it, but the fact is that PL/SQL and *what not* is not even what the discussion about, the discussion is about keeping your database application seperate from your client application that uses the database
<1> rmah, how do I make sure that child process is actually dying?
<2> and if you've had "more headaches" from stored procedures, it's probably because you didn't have the right level of role separation.
<3> tag: no, what you're talking about is placing business logic into a seperate section of code (stored procs)
<2> no
<2> I'm not
<2> and that's where you're mistaken
<3> a section that has no encapsulation, no namespace management, no object support, etc.
<3> and I hate that
<2> I'm talking about placing DATA BASE APPLICATOIN logic in stored procedures
<3> all applications are database applications
<2> no
<3> well, all of the ones I work on
<2> not all applicatoins are database applications
<2> and not all data driven applications use relational databases
<3> 90% of business apps are
<2> I am talking about making a logical separation between the application that does the data crunching, and the application that utilizes the results of the data crunching.
<2> which isn't necessarily business logic, the business logic is quite probably and almost always, found both the data application and the application (or applications) using the data application
<3> and I'm saying that I'd rather have the data crunching in an environment where I can manage the code (with packages, namespaces, objects, etc.)
<0> rmah++
<2> rmah: Then you don't use a relational database.
<2> or only use a relational database for certain parts of your application
<3> tag: so you disagree, big deal
<2> I disagree with having Perl / SQL / PL/SQL / HTML in the same piece of source code
<3> I've had to deal with systems that are 10 or 20 years old with *thousands* of stored procs that are poorly named, poorly documented, poorly organized (if at all
<2> under any conditions
<3> and it's HELL
<2> the last three parts are why it was hell
<3> three times at three companies. it's ****ing hell
<2> the fact that they were stored procedures had nothing to do with it
<3> most places are like that (from my conversations with others)
<3> tag: actually it does
<2> they could have been poorly named, poorly documented, poorly organized object methods with ****ed up inheritance chains
<2> it would have still been hell
<2> HELL I tell you
<3> because stored procs have no means of organzizing them
<2> I've worked on applications that have HUNDREDS OF THOUSANDS of quieries in string literals in source code
<2> every which ****ing way
<2> and that, is hell
<2> complete and total hell
<2> rmah: yes, that ****s
<6> I sense rmah is dangerously close to the fallacy of composition
<3> heh, at last we agree on something. quick! find something to argue about!
<7> emacs!
<5> vim!
<3> revdiablo: if I knew what that was, I might take offense
<2> reality is SQL ****s anyway
<3> true, but it's what we have
<3> damn Codd and Date!
<8> should CGI::Session work with mod_perl2?
<3> virgomoon: yes
<8> damn
<3> erm, probably
<8> lol
<8> then I'm doing something stupid
<8> thanks
<0> rmah, wazza, codd and date giving problems? Eternal discussions arise :)
<3> I organize my money (all facing the same direction, etc.)... that's how anal I can be!
<1> ****ING PERL PROFILER
<3> poor MrBIOS
<9> that is not how you use it!
<1> no errors, NOTHING to go on
<1> I detest **** like this
<3> you were happier when you were getting "not found in @INC" errors?
<1> rmah, at least I knew how to fix it with relative ease
<1> now I'm chasing ghosts
<3> ok, you put the entry into your startup.pl?
<3> the use line
<1> no, I put it in the httpd config
<1> PerlModule Devel::Profiler::Apache;
<2> rmah: where I can, I like to use object oriented databases for persistence
<3> tag: O
<3> tag, I'm not a big fan of OODB's
<3> anyway
<3> MrBIOS, ok, what's your serverroot?
<2> And for things like persistence, they are faster anyway
<1> rmah,
<1> rmah, /etc/httpd
<1> in /etc/httpd is a logs symlink to /var/logs/httpd
<3> and you have a logs directory there?
<3> please ls -l /var/logs/httpd
<1> wait a sec
<3> erm, ls -ld
<1> Tue May 30 20:15:12 2006] [error] Can't locate object method "server_root_relative" via package "Apache" (perhaps you forgot to load "Apache"?) at /usr/lib/perl5/site_perl/5.8.7/Devel/Profiler/Apache.pm line 22.\nBEGIN failed--compilation aborted at /usr/local/cs/lib/apache_startup.pl line 5.\nCompilation failed in require at (eval 2) line 1.\n
<3> haha
<1> the PerlModule way wasn't working
<1> but putting it into my apache_config.pl works
<3> how odd
<1> yes
<3> virtual server
<3> ?
<1> the same file apache config file calls the apache_config.pl file
<2> mod_perl ****s
<1> rmah, yep but this part is global
<1> tag, tell me about it
<2> well
<2> it's cool if you're writing a tiny apache module
<2> but it's not cool if you're trying to build like a web application
<1> which is exactly what they bought
<3> I prefer FastCGI actually
<7> jboss! dun dun dun!!
<3> J2EE is fine for some things but damn, the setup ****s
<2> thrig: I don't really understand why anyone uses those "All in one J2EE Packages"
<2> thrig: like you know, java enterprise server, jboss, etc.
<3> tag: sometimes you need **** like RMI, distributed objects, distributed transactions, etc.
<2> thrig: nobody writes a J2EE app that uses all of J2EE anyway
<7> neither do I. I just support the apps that don't know how to daemonize themselves
<2> rmah: that's fine
<3> tag: not true
Return to
#perl
or
Go to some related
logs:
out of scan range centos
ununtu reset xorg
perl golf rindolf
Parse error: syntax error, unexpected T_VARIABLE, expecting T_FUNCTION in
debian mythgame
#ai
#physics
box css transparent corner images
overclock X600 passive-cooling
gentoo libqavm
|
|