How ColdFusion ORM deals with changes outside of ORM

I just started learning ORM ColdFusion and persistent cfcs and how it can improve application performance. I am still working to get a complete understanding before trying to implement anything on my own sites, but there is one question that I seem to be unable to find anywhere.

I understand that most of the performance gain comes from the CRUD batch database in one transaction at the end of the page and from the intelligent caching of the selected statements. Regarding the latter, how this caching works, and more specifically, how it relates to changes made outside of the ColdFusion application.

For example, suppose I have a user table that looks like this:

Hair Name

Nick Brown

John Blonde

Now suppose I run a simple update request through PL / SQL Developer to update John's hair color to black. Now...

  • What happens the next time the page tries to list John's hair color?
  • Assuming the hair color is still displayed as blonde because it is cached, how can I clear this cache?
  • Assuming hair color is still cached like a blonde, what happens if I change John Jonathan's name using CF ORM? Will he rewrite the hair color back to the blonde when he updates the line?
  • Similarly, if I try to update my hair color to green with CF ORM? Will CF check and notice that its cached value (blonde) is no longer the current value (black) and gives some kind of feedback?

(, ), , CFQuery John . , CFQuery ORM?

CF, -, ORM , (CFQuery, PL/SQL ..), . .

.

+3
3

"", , Hibernate, , ColdFusion. :

ColdFusion Nicks hair Red. .

SQL SELECT *... . Blond.

ColdFusion Nicks ORM, - Blond.

, , , .

+2

, .

.:

ormEvictCollection(), ormEvictEntity() ormEvictQueries()

+1

, - - . , , . ORMReload() , ColdFusion. , , , " 1, 0" CF.

+1
source

Source: https://habr.com/ru/post/1778769/


All Articles