Adding a new field causes an error: field 'query' does not exist

You didn't run update.php the last time you updated code, did you?

@merlin, I'm getting this too and update.php says I'm up to date.

views_update_12() has this which shows it dropped query.

$ret[] = update_sql("ALTER TABLE {view_view} DROP query");

This is a bug in _content_views_rebuild_views() it looks like.

Yes, content.module is not yet updated to account for latest cache changes in views-dev

Oh. 'query' disappeared in the -dev version. I didn't realize anyone external was utilizing queries which checked this field. That's somewhat unfortunate.

No, it's alright - and I was perfectly aware of that when I submitted the 'cache' patch - AAMOF, I submitted it just to get rid of _content_views_rebuild_views :-)

I was just not sure of when to update CCK accordingly. I guess I was waiting for Views 1.6 to be released.

The bug that was holding me back has been found and a patch has been submitted, but I have to find the time to sit down, clean up a few things and roll a release. And my baby shower is this weekend which means the in-laws and such will be here. But also my best friend from out of town too. Which is good, but likely to not be a programming friendly environment!

no pressure intended ;-)

Actually, when Views 1.6 does get out, CCk will have to release a matching version straight away, so I guess it's best to commit the cck fix now and have a little time to make sure everything is OK.
Plus Karen just committed a first compatibility fix, so I went ahead and committed the rest.
CCK 1.x now targets Views 1.x (I added a note on CCK's project page about it)

Earl : can you drop us a note before you release Views-1.6, so that we can be fast on releasing our matching CCK ?

You marked the other issue duplicate, so I'd better move my comment here.

I'm worried that we won't know what version of Views people are using, so how do you plan to handle that? I don't think we can require a certain version of Views, or are you thinking we can?

I don't think we can require a certain version of Views, or are you thinking we can?
Actually I was thinking we could.
Besides, it's not actually 'requiring', since using the updated CCK with a non-updated Views will not _break_ anything - you 'just' lose the automatic refreshment of cached Views query when your field definitions change.

Keeping some logic in CCK to determine which version of Views is running and branch accordingly would be adding cruft IMO, I don't think I'm willing to maintain this kind of compatibility checks.
Simply adding a drupal_set_message in a CCK update function, advising the admin to update to Views 1.6 should be enough. What do you think ?

That's why I asked, I wasn't sure what your plans were. I think if nothing will be broken (except that Views won't update) that is OK because if anyone has issues we can just say 'Get the latest version of Views). So I'm OK with that.

How about this: I'll make the tag when I'm ready, and send you a contact message, and when you're ready I can make an actual release from the tag.

Deal :-)

Earl has released Views 1.6, and CCK 1.5 is out too :-)