when I storing the field in database, it stop show to me on node

What you are describing is not normal. The point of the computed field is that it shows on the node view.

Make sure the "Display Format:" box has:
$display = $node_field_item['value'];

Hi

I have exactly that format in display:
$display = $node_field_item['value'];

Normally I see all my computed fields on node. But when I chceck "store using database...", it disappears.

Thanks for the help
Igorik

Another possibility is the Default Value in the database storage settings. Try to delete the 'test2' and see if that helps.

There can be problems using the default value with the text datatype.

I know it's been a while, but are you still having an issue with this? Database storage for Computed Fields shouldn't affect their display, and I haven't seen this happen personally. If you have any further information, I can try testing it out here though.

I have this exact same issue. Everything works fine when I don't tell it to save to the database. But when I do, it does not display and it does not get stored, no matter what I'm trying to store, and I've tried leaving it as null or not, and typically tested with default set empty.

Hi stickybenson, I didn't try it for a while, but there was a changed concept aabout month ago with latest version and data are not storing into db but into files or something else I think. Read latest issues and try the latest module version.

Version: 6.x-1.0-beta2

I am getting the same thing. It completely tricked me, I spent about 1/2 hour staring at each character in the example to make sure I had everything right, but nothing would show in the computed field, until I turned off the database storage option.

This is surely a bug.

I upgraded to 6.x-1.0-beta3 and it is still broken.

As soon as I select 'Store using the database settings below' the computed field vanishes.

I need to be able to access the computed field from Views, so I need the database storage option.

Very grateful for attention to this soonest,

Webel

My trouble occurs with 6.x-1.0-beta3 vs. Drupal 6.8.

If anybody has managed to get 6.x-1.0-beta3 working could you please confirm that and post a minimal example here, along with the Drupal version. As far as I can tell 6.x-1.0-beta3 is broken, one can't store to database, and so one can't use views of computed fields, which compromises this promising module.

Q: When was the last version known to work together with Views ?

I am using a few Computed Fields with 6.x-1.0-beta2 and I am storing the fields in the database. I am using the varchar data type and setting a data length.

Several months ago I did see a problem using the text data type. Please try varchar.

Moonshine has kindly assisted me with this clarification (extracts from email):

DB stored "computed code" values are computed and stored to the DB when nodes are *saved* or *edited*. So if you have a bunch of existing nodes that were created before you switched to db stored fields, don't expect them to have computed values in the db until they are saved again. Display output code on the other hand is triggered (if used for display) when the field is displayed.

That was exactly my problem.

However if the display output code uses the computed value, which most people do, and that computed value isn't in the db yet, it won't have anything to work with.

And that was what I overlooked.

Thanks for clarification, it works now, however I have to edit and resave a couple of hundred nodes,

Webel

Same bug but I discovered a work around by simply resaving the node. See this post on issue que.

http://drupal.org/node/627010