node_load is still your friend. No real change there, you don't have to worry about the entity layer. <div><br></div><div>field_get_items will get you the values of the body field in the correct language. <br><br><div class="gmail_quote">
On 24 January 2011 14:16, Blaine Lang <span dir="ltr"><<a href="mailto:Blaine.Lang@nextide.ca">Blaine.Lang@nextide.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
> You should probably not be using the DB API to load the field value.<br>
> Since (in theory) we are able to have our actual field data stored in<br>
> various back-ends, you should only really load the data via node or<br>
entity<br>
> loading functions.<br>
<br>
> The node table itself is still reliably in Sql though, so you can<br>
select<br>
> which node to display via the DB API.<br>
<br>
> Peter<br>
<br>
I agree peter and that's why I was exploring the entityController class<br>
but did not see a good example of how I would do what I need - return<br>
the body field for the node of type 'frontpage_quote'.<br>
<br>
I originally needed a random result and the site is only going to have<br>
10 at most so performance is not an issue as this is a light weight<br>
marketing site, but I appreciate the DB questioning/ideas on the random<br>
issue.<br>
<font color="#888888"><br>
blaine<br>
<br>
<br>
</font></blockquote></div><br></div>