Get an error installing since the schema for views_view indicates field view_php is a blob with a default value. Since blobs may not have a default value the error occurs.
below is a snippit of the schema from views.install (lines 45 - 49)

      'view_php' => array(
        'type' => 'blob', 
        'default' => '',
        'description' => t('A chunk of PHP code that can be used to provide modifications to the view prior to building.'),
      ),

to fix the error it should be

      'view_php' => array(
        'type' => 'blob', 
//        'default' => '',		// BLOBS CANNOT HAVE DEFAULT VALUE
        'description' => t('A chunk of PHP code that can be used to provide modifications to the view prior to building.'),
      ),
CommentFileSizeAuthor
#2 views2-blob-default.patch614 bytescsevb10

Comments

kwikone’s picture

kwikone commented
Status: Closed (works as designed) » Needs review

OOps, was in too much haste and selected wrong status :-)

csevb10’s picture

csevb10 commented
StatusFileSize
new views2-blob-default.patch614 bytes

This worked for me both ways (using MySQL 5.0.41). Are you using MySQL (if so which version) or PostgreSQL? I've attached the patch file that corresponds to what you have above.

kwikone’s picture

kwikone commented
Status: Needs review » Reviewed & tested by the community

Yes, MySQL Version is 5.0.51
Also, the schema module flags it as well.
Patch looks good.

s@ilor’s picture

s@ilor commented
Assigned: Unassigned » s@ilor
Category: bug » support
Status: Reviewed & tested by the community » Active

Hello,

Permit me to ask; how do you apply this patch? Apologising for my low-tech standards ...

Cheers,

s@ilor’s picture

s@ilor commented
Title: Get error installing table views_view » Get error installing table views_view II

Hi again,

Is this related to this error?:

recoverable fatal error: Object of class stdClass could not be converted to string in C:\xampp\htdocs\drupal6\sites\all\modules\views\includes\cache.inc on line 110.

merlinofchaos’s picture

merlinofchaos commented

If you have to have patching described to you, then you qualify as someone who should NOT be attempting to use Views 2 at this time. Please read the warnings on both the release node and the project page.

merlinofchaos’s picture

merlinofchaos commented
Title: Get error installing table views_view II » Get error installing table views_view
s@ilor’s picture

s@ilor commented

Thank you for this excellent answer. It really helps bridging the community.

Just thought that, even my modest contrib and interest could be of some use; "They more who is using and testing the themes and modules, the more chance there actually is of discovering possible flaws in the code"

How does this sounds to you?

merlinofchaos’s picture

merlinofchaos commented

Yes, that's fine, but Views 2 is not in a state where people who aren't *very* familiar with it can test it. That's why I put *dire* warnings on the page. All it can do right now is confuse and frustrate you, because it is very much *in progress* and from the perspective of a user, *absolutely nothing works*.

And I've been trying to keep people away from it so that you don't waste your time, and subsequently waste my time. Is that hard to understand?

merlinofchaos’s picture

merlinofchaos commented

Let's be honest. Did you even read the warnings I put up? Or did you read them and assume they do not apply to you?

s@ilor’s picture

s@ilor commented

You know, why don't you direct your rant somewhere else? You did not have to answer at all. Perhaps you noticed the two other persons opening this thread. It might be that one of them would feel the inclination to answer my question.

Remember; it's not me wasting YOUR time ....

Peace,

merlinofchaos’s picture

merlinofchaos commented
Status: Active » Closed (fixed)

Ahh, so you read it and believed it does not apply to you. It does. Here's the part that truly applies:

If you are 1) not a developer and 2) not an expert developer and 3) don't feel really comfortable with Views' code, DO NOT INSTALL THIS.

If you can't answer true for 1, 2, AND 3, and install this, and then file issues, I reserve the right to mock you mercilessly, and probably angrily, for wasting your time and my time.

I read everything that comes through this issue queue. I am a responsible maintainer. It is, apparently, too much to ask that you actually read anything I put out there. Fine, if you want to be frustrated, go ahead. Ignore the warnings, use the software. Or at least, try to. I happen to know you can't, but don't let that stop you. You CLEARLY know better than the author of the software.

But be forewarned: you are now on my shit list. Any issue you open will be summarily closed, without response. You're right, I don't have to respond to you, but I do have to keep my issue queue clean. Or at least try to. People like you make it very hard.

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented

"Remember; it's not me wasting YOUR time ...."

When someone files issues against code that is very clearly labeld as in progress and not being ready for use, it takes the maintainer time to deal with it which could be use towards finishing said module. You may not have been the OP, but by asking questions on this issue, you keep popping it back up in the issue queue and causing him to take more time. So, yes, it _is_ a waste of his time. And you are not the first. The number of people ignoring his warning and attempting to use this very much unfinished module is enough to try the patience of a saint.

Michelle

zilla’s picture

zilla commented

here here...i more than agree. set up a d6 site, went for views and realized that i should just focus on building out everything else for a month or so while the testing continues (also waiting for organic groups, which is dependent upon views and will run around a week behind)...can't wait to see all of the new features and utility inside drupal 6 and thanks for working on this!

drunkensailor, maybe you should wait a couple of weeks and see if a dev release marked as 'stable but test (beta) is out, at which point you could point out bugs and all of that...not sure when exactly that will be, but it sounds like the current version will cause nonstop issue postings and the dev clearly has a punchlist in front of him already...