7303 update fails

Sounds like a duplicate of http://drupal.org/node/1233010 as services just uses core update functionality

I'm seeing the same thing. I think it's a core issue with postgresql. Are you using this marcjohnson?
I'm getting the following message the first time I run update.php:
Failed: PDOException: SQLSTATE[23502]: Not null violation: 7 ERROR: column "server_settings" contains null values: ALTER TABLE {services_endpoint} ALTER server_settings SET NOT NULL; Array ( ) in db_add_field() (line 2781 of /Users/ottob/Sites/drupal7/includes/database/database.inc).

The next time it says that the server_settings column already exists, which it does. But only as bytea, no constraints or description.

If I modify includes/database/pgsql/schema.inc about line 371 like this:

     if ($fixnull) {
+      $this->connection->query("UPDATE {" . $table . "} SET $field = ''::bytea");
       $this->connection->query("ALTER TABLE {" . $table . "} ALTER $field SET NOT NULL");
     }

I'm a bit short on time right now, but will create a proper issue for core soon.

It's not duplicate of #1233010: 7.7 update did NOT update!. Reopened.

This is caused because the new field is forced to be NOT NULL.

   'not null' => TRUE,

Here's a patch. Delete the field "server_settings" from "services_endpoint" if exists before rerunning the update script.

But isn't it reasonable to have the server_settings fields as NOT NULL? In core for instance the parameters fields of the actions table is also bytea NOT NULL. Your solution feels more like a workaround.

Reported to core: #1240304: addField issue with not null blobs on PostgreSQL

While there are endpoints that doesn't have "server_settings" it seems reasonable for me to allow NULLs for this field. So, not only a workaround...

This should work if keeping not null is preferred. See Damiens comment in #1240304: addField issue with not null blobs on PostgreSQL.

I don't see the reason of having this field as NOT NULL while there are records where "server_settings" is N/A (the real world "N/A" has to be read as "NULL" in the virtual world). Don't want to insist more on this subject...

Same with me

Log says:

The following updates returned messages
services module
Update #7303

    Failed: PDOException: SQLSTATE[01000]: Warning: 1265 Data truncated for column 'server_settings' at row 1: ALTER TABLE {services_endpoint} CHANGE `server_settings` `server_settings` LONGBLOB NOT NULL COMMENT 'The server settings for the endpoint.'; Array ( ) in db_add_field() (line 2781 of includes/database/database.inc).

After reading damz comments I'm happy to rbtc this and bumping to major as this blocks an upgrade path.

Im at a conference until monday, Marcingy if you want to commit, go for it.