• Quick note - the problem with Youtube videos not embedding on the forum appears to have been fixed, thanks to ZiprHead. If you do still see problems let me know.

Drupal/database questions

bug_girl

Master Poster
Joined
Nov 30, 2003
Messages
2,994
I am still struggling with the Drupal site I inherited. I'm talking to a couple of developers about taking it over, but they've asked two questions that stumped me. I wanted to check the funny feeling in the pit of my stomach with you all.

1. They want admin access to look at the database structure before they can give us a firm quote. This, I can understand--it could be a total cluster* and they don't want to walk in blind--but it makes me nervous. Thoughts?

2. They asked me to give them a database dump. I...have no idea how to do that. Now, I did manage to update 27 modules + the drupal core without crashing the interwebs, so I'm sure *eventually* I will figure it out.
But, if anyone happens to know where simple instructions are and could point me to them, it would be greatly appreciated.

Thanks!
 
I am still struggling with the Drupal site I inherited. I'm talking to a couple of developers about taking it over, but they've asked two questions that stumped me. I wanted to check the funny feeling in the pit of my stomach with you all.

1. They want admin access to look at the database structure before they can give us a firm quote. This, I can understand--it could be a total cluster* and they don't want to walk in blind--but it makes me nervous. Thoughts?

2. They asked me to give them a database dump. I...have no idea how to do that. Now, I did manage to update 27 modules + the drupal core without crashing the interwebs, so I'm sure *eventually* I will figure it out.
But, if anyone happens to know where simple instructions are and could point me to them, it would be greatly appreciated.

Thanks!


MySQL dump
 
Too lazy. But thankfully others have taken the time to explain it.

And this guy doesn't even mention the fact that Drupal (unless this changed recently) doesn't use any classes or OOP. Fail, fail, fail.
 
Well, Drupal is not my favorite CMS. But there are things about it that are very nice. It's great that the security updates are built into the structure!

But, the database stuff is waaaay beyond what I have time to do, as a volunteer.
 
Too lazy. But thankfully others have taken the time to explain it.

And this guy doesn't even mention the fact that Drupal (unless this changed recently) doesn't use any classes or OOP. Fail, fail, fail.
I have no clue about the pros and cons of Drupal. Notwithstanding, the critique you link to is clearly moronic, what with the complaining about certain data/metadata being stored in a database.
 
I read those, and they are full of BS, sorry. There were no excuses whatsoever to NOT use classes and OOP even back in PHP4's primitive OOP days, and now that PHP5 has been out for years and PHP6 is on the way, well...
I'm too lazy to elaborate, but I've been doing PHP for over 8 years, and I can safely say that I would never, ever accept a job working with Drupal, even if it was twice the salary I'm used to get. No freaking way I'm ever touching such spaghetti.

I disagree that Drupal is as bad as you suggest. I used it and found it not that difficult to use.

But it may be a matter of opinion. ;)
I am speaking from a programmer's perspective, not a user. I have no idea if it's worth something as a CMS from a user-perspective. Maybe it is. But, like Joomla, it's a nightmare to work with when you need to do any sort of custom application.

(You might say, "but it's a CMS, it shouldn't be used as a framework for creating custom apps!", and you'd be 100% right. Unfortunately, try telling that to most idiot project managers... I quit my last job because of Joomla because I was so miserable. My only consolation at the time was, "hey, at least it's not Drupal!". True story.)

I have no clue about the pros and cons of Drupal. Notwithstanding, the critique you link to is clearly moronic, what with the complaining about certain data/metadata being stored in a database.
How in the hell is that moronic? Storing views or templates in the database IS retardedly bad software design. Good-bye version control, hello countless and needless SQL queries and the need for even more caching. Ugh.
 
...
How in the hell is that moronic? Storing views or templates in the database IS retardedly bad software design. Good-bye version control, hello countless and needless SQL queries and the need for even more caching. Ugh.

You know, I have toyed with the idea of having a ClearCASE-based web server. Then everything is stored in a database, but that fact is hidden from apache which deals with everything as though it were a flat-file site.

All version-controlled, you roll out a new CSS template by changing the production view.
 
How in the hell is that moronic? Storing views or templates in the database IS retardedly bad software design. Good-bye version control, hello countless and needless SQL queries and the need for even more caching. Ugh.
What caught my attention was the writer foolishly having his/her undies in a bunch over logs in the DB.

(I don't know what a "view" is in Drupal speak, but as you're no doubt aware, sql views are indeed stored in sql databases, and well they should be.)
 
Yeah, logs in the database isn't such a big deal, but I still wouldn't consider it terribly good design. Nothing I'd write about, though.

But FYI, "views" here are referred to in the MVC sense, not in the SQL sense. Obviously... or so you'd think. -_-
 
Well, Drupal is not my favorite CMS. But there are things about it that are very nice. It's great that the security updates are built into the structure!

But, the database stuff is waaaay beyond what I have time to do, as a volunteer.

There are easier options, but it is versatile one you figure some things out. Admittedly it is a steep learning curve potentially though.
 

Back
Top Bottom