text:
Empty chair, broken promises, empty suit.
"Empty chair, broken promises, empty suit"
In a futile attempt to recover from a disastrous "performance" in the first 2012 presidential debate, President Hussein Obama's puppet masters explained he was "off his game." I've got news for you Mr. Obama, being elected the leader of the free world is not a game.
Fast forward to debate #2. The president said he was offended by the suggestion that anybody on "his team" would intentionally withhold the truth about what happened in Libya or use the tragedy for partisan purposes. In that regard, I offer these remarks: (1) Nobody, including Governor Romney and Congressman Paul Ryan, made such a suggestion, so may we assume that the president or his team is doing exactly that…trying to use this tragedy for his political advantage? (2) Why is it so difficult for President Obama to use the words "terrorist attack?" The attack at the American Embassy in Libya on September 11, 2012 was a tragedy and it was, without any doubt whatsoever, a terrorist attack. And, your post-attack actions were, quite clearly, politically motivated. Everyone in American including Reverend Jeremiah Wright, Bill Ayers, David Axelrod, Valerie Jarrett, David Plouffe, Michelle Obama, your kids, the Cheshire Cat (Joe Biden) and Barrack Obama knows that. Consider yourself offended, Mr. President.
Yes, on the 11th anniversary of the 9/11 terrorist attacks right here is America, the attack in Libya was no less a terrorist attack than when Army Major Nidal Hassan assassinated 13 soldiers and wounded many others at Ft. Hood, Texas on November 9, 2006. Yet, our naïve, game-playing, politically motivated president insists it was a case of "workplace violence." It makes one wonder what this president's agenda is, but after 45 months in office his agenda has become quite clear…appeasement. Shame on you Mr. President and your "team" for perpetuating a cover-up far more egregious than Watergate…you have permanently etched Banghazigate as your enduring legacy…a massive cover-up. Have you not learned that the cover up is often far worse than the crime itself?
The November 6, 2012 presidential election is not a game Mr. President yet you are playing a dangerous one with the future of America and I, for one, do not appreciate it.
Recently, the president paraphrased the words of President Harry S Truman by suggesting the buck stops here, most of the time. What he means, is when it is convenient for him to do so. But with the election just over two weeks away he has decided it was far easier to have Secretary of State Hillary ('after three years in the White House I just came across these Rose law firm records in my closet') Clinton take the fall. And Obama says his opponent is waging a war on women? Who is he kidding?
Before deciding who to vote for on November 6th let's give credit where credit is due.
• Unemployment among blacks, Hispanics, women, and young people is more than 2 percent higher than the disgraceful national average of over 8% for 44 of the last 45 months. The President is responsible for that.
• Unemployment conveniently dropped just below 8% last week but one wonders what it would have been if California had reported its numbers in time for that report. And one wonders how much higher unemployment would have been if President Obama's Labor Department had not ordered Lockheed-Martin to delay laying off 122,000 workers until after the election. The President is responsible for that.
• President Obama promised to cut the budget deficit in half, yet in each of the last four years we have seen a deficit of over one trillion dollars. The President is responsible for that.
• President Obama promised to cut the national debt, yet it has grown from under $10 trillion in 2008 to over $16 trillion in 2012. The President is responsible for that.
• The Braken Bat Cave Meshweaver spider has been declared an endangered species thus halting an important $15 million highway underpass project in San Antonio, TX. The President is responsible for that. Suggestion: If you see one of these dangerous (sorry, Mr. President, endangered) species step on it immediately.
• Mr. President, is Ms. Clinton also willing to take responsibility for the green energy companies into which you poured $90 billion dollars and which are, one by one, quickly falling into bankruptcy. And is it is any coincidence that many of these companies were owned by your campaign contributors? It seems these "investments" were primarily motivated for political gains.
To paraphrase a Governor Romney remark made at the Al Smith dinner in New York City last week, the last four years and this article were brought to you by the letter "O" and the number $16 trillion. Brilliant, Governor!
The President has a penchant for hanging with such celebrities as Miami radio talk show host, the "Pimp with a Limp," the ladies of The View, Eva Longhoria and other Hollywood mental giants rather than world leaders visiting the United Nations. While it might be characterized as an interesting campaign strategy, I remain unimpressed. This president was unqualified for this office and he has done nothing to change my mind. He has proven to be a lightweight. He is our 'president in absentia,' totally disengaged.
President Obama's campaign has been one of division and anger...and in two debates he has resorted to mischaracterize Governor Romney's record and solutions for the future. But when you have no positive record to stand on yourself and nothing to show after more than 100 rounds of golf what else can he do?
Clint Eastwood nailed it. Empty chair, broken promises, and an empty suit.
Mary Kaplan October 23, 2012 at 9:50 AM
Ok, it is obvious from your post that you are not fond of President Obama or his actions over the last 4 years. When you say that he mischaracterized Mitt Romney's record and solutions for the future, isn't this the name of the political campaign game? Mud slinging from both sides seems the norm.
Walt Coogan November 3, 2012 at 4:41 AM
My goodness, Mr. Crank, your understanding of the economy and the government is extraordinarily simplistic, fallacious, and delusional. Indeed, the Republicans in Congress deserve at least as much blame for most or all of these criticisms as President Obama. And calling him "Hussein Obama" suggests that you are racist or xenophobic, for you're obviously insinuating that he's not a real American just because he possesses a name with "exotic" origins that coincidentally dovetails with a former US enemy. The fact that you possess this platform for your adolescent, ignorant, clueless rants proves embarrassing.
Whoops, I meant Mr. Madison. Sorry, Mr. Crank, I saw the advertisement banner at the top of the screen and mistook you for the author.
I haven't watched the debate yet, I guess only half of it. I noticed that Obama and Romney was in a hot seat that time and some pueblo bankruptcy attorney find it a bit annoying at times.


Sammamish locksmith guarantees the best experienced service to each of our customers in addition to the speediest arrival time and the actual best deals in the locksmith current market. our very own locksmiths at Sammamish Locksmith experience much training program so that you can be qualified for the most tough locking issues. Our own locksmiths at Sammamish Locksmith are capable of managing with literally all kinds of lock and also with all kinds of an urgent lockout.
Our skilled locksmiths at Sammamish Locksmith can put on the required safety measures that will assure that you get relaxation andpeace of mind when you need it. .
Sammamish Locksmith could certainly commit to a 15 minute response time period, which is certainly among the speediest time frames around the locksmith industry. Our purpose at Sammamish Locksmith is always to preserve our very own clients from waiting a long time for a locksmith, and also to be sure that our clients are ready to keep on with the program of their own day as swift as you can.
Sammamish Locksmith offer transponder microchip key production, file cabinet locks, gate locks, locked safe opening, emergency trunk and glove compartment opening, as well as much more. Sammamish Locksmith definitely will discover if a malfunctioning lockset is as a outcome of a issue while in the latch installation or maybe it is with the lock device. We will then recommend the complete answer to get this particular issue as well as your lock will commence working regularly.
Automotive- Sammamish Locksmith will perform everything to help you get in the car as quickly as possible and be sure you will continue with the routine of the day very quickly. Each of our locksmiths at Sammamish Locksmith are going to supply you and your family along with products to automotive problems just like replacing busted elements, ignition changes, VAT key duplications, taking out busted keys, unlocking cars and trucks and trunks, key slicing, creating chip keys, transponder key encoding and a lot more.
Commercial- you can find different commercial services we present at Sammamish Locksmith that come with things such as business door unlocking, file cabinet systems, replacing locks, putting in commercial safes, control systems and master controls, panic rooms and panic bars, keyless entry units, business locks rekeying as well as a lot more.
Residential- to help make guaranteed that your protection and also your family's is at the appropriate hands you need to be certain of the fact that locksmith company you've selected is pro and also trust worthy. Our locksmith professionals at Sammamish Locksmith are specialists as it reaches to delivering residential products and services and therefore are ready to assist you anytime. These locksmiths can easily take care of residential troubles including home door unlocking, fixing locks, gates and doors, adding peepholes, rekeying locks, opening up safes and letters boxes, changing and fixing locks, extracting keys, new installations and more services.
Sammamish Locksmith specialists are highly professional and so are skillfully trained to handle all sorts of locksmith and protection problems. We now have the very best team around to provide you with the highest quality of locksmith solutions. Only Sammamish Locksmith provides the clearest security services.
Sammamish Locksmith safety services and products utilize the most innovative technologies and apply exactly the most professional knowledge for household, business office and motor vehicles. Sammamish Locksmith presents top-of-the-line locksmith product or service at absolutely the best competitive prices in the business.
Sammamish Locksmith knows your locksmith and safety needs. Contact us at this moment at 425-880-3755 for free examination. Our certified staff will answer all your queries relating to your locksmith worries and furnish you free estimate as well.
Have you locked your self out of your property? Do you require brand new locks to your household? If you require residential locksmith and safety service then Locksmith Sammamish will be here to offer you. If you'd like emergency service you are able to give us a call at 425-880-3755 anytime round the clock. If you do not need emergency situation locksmith service, you are able to contact us to put together an appointment so that we can aid you together with your residential locksmith needs at your convenience.
Our locksmiths are highly trained and highly capable to provide you with the excellent assistance you should have.
when your company is needing a locksmith plan to meet your whole commercial locksmith needs then give Locksmith Sammamish a telephone call: 425-880-3755 . Locksmith Sammamish can be your visit guy in regards to locksmith and safety services.
Our very skilled professional technicians possess the most updated locksmith equipment and tools for any industrial locksmith needs. We have been continuously adding the newest locksmith and home alarm system services to the constantly growing number of services to offer our customer full satisfaction. Whatever your business safety needs are phone us at 425-880-3755 and we all can provide you with a free quoted price about the locksmith services which you will want.
Have you lost or busted your motor vehicle key? Must you make your door unlocked? If you would like quickly specialized locksmith service to your automotive then Locksmith Sammamish is here now to support you.
With our state-of-the-art equipment along with our pleasant and also qualified qualified locksmith professionals, we promise rapidly and trustworthy service for you personally vehicular lock needs. Within fifteen minutes of hanging within the phone as soon as you call us, we can dispatch the closest locksmith to you this means you don't have to bide time until lock repair, key repair or replacement.


text:
Justia Dockets & Filings Ninth Circuit Arizona District Court Cervantes v. Countrywide Home Loans, Inc., et al Filing 222
Cervantes v. Countrywide Home Loans, Inc., et al
ORDER that: Dft Tiffany & Bosco, P.A.s Motion to Dismiss is granted 44 ; Dft GMAC Mortgage, L.L.C.'s Motion to Dismiss Plas' First Amended Complaint [118 is granted; Dfts MERS and MERSCORP, Inc.'s Motion to Dismiss 122 is granted; D fts Freddie Mac and Fannie Mae's Motion to Dismiss 123 is granted; Dft United Guaranty Corporation's Motion to Dismiss 124 is granted; Dfts National City Corporation and PNC Financial Services Group, Inc.'s Motion to Dismiss 126 is granted; Dft GE Money Bank's Motion to Dismiss 127 is granted; Dfts National City Bank and National City Mortgage's Motion to Dismiss 128 is granted; Dfts Countrywide and First Franklin's Motion to Dismiss 133 is granted; Dft Wells Fargo's Motion to Dismiss 137 is granted; Dft HSBC Mortgage Corporations, U.S.A.'s Motion to Dismiss 139 is granted; Dft JPMorgan Chase Bank, N.A.'s Motion to Dismiss 147 is granted. FURTHER ORDERED that Dfts Countrywide Ho me Loans, Inc., Bank of America, N.A., Merrill Lynch & Company, Inc., First Franklin Financial Corporation, and LaSalle Bank, N.A.'s Motion for Leave to File Sur-Reply 166 is denied as moot. FURTHER ORDERED that Plas Olga Cervantes, Carlos Alm endarez, and Arturo Maximo's Motion to Amend Complaint 189 is denied. FURTHER ORDERED that Dfts' Motion to Transfer and Consolidate 194 is denied as moot. FURTHER ORDERED that Dft Tiffany & Bosco, P.A.'s request for attorneys' fees is denied without prejudice, with leave to re-file pursuant to LRCiv 54.2. FINALLY ORDERED that the Clerk of the Court shall enter judgment accordingly. Signed by Judge James A Teilborg on 9/23/09.(KMG, )
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 WO IN THE UNITED STATES DISTRICT COURT FOR THE DISTRICT OF ARIZONA (1) Olga Cervantes, an unmarried woman,) et al., ) ) Plaintiffs, ) ) vs. ) ) ) (1) Countrywide Home Loans, Inc., a New) ) York corporation, et al., ) ) Defendants. ) _________________________________ ) No. CV 09-517-PHX-JAT (Lead) ORDER Pending before this Court are numerous motions to dismiss by various party Defendants, Plaintiffs Olga Cervantes, Carlos Almendarez, and Arturo Maximo's Motion to Amend First Amended Complaint (Doc. # 189), and Defendants' Motion to Transfer and Consolidate (Doc. # 194). For the reasons that follow, the Court denies Plaintiffs' motion to amend, denies Defendants' motion to consolidate as moot, and grants the various motions to dismiss.1 BACKGROUND In September 2006, Plaintiff Cervantes refinanced her residence by executing a promissory note and deed of trust in favor of Defendant Countrywide Home Loans, with 1 Several Defendants have joined in various motions to dismiss and/or replies in support of motions to dismiss. To the extent the Court need address these joinders, they are granted. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Mortgage Electronic Registration Systems, Inc. ("MERS"), listed as the beneficiary. In December 2006, Plaintiff Almendarez purchased his residence through entering into a promissory note secured by a deed of trust in favor of First Franklin, with MERS listed as the beneficiary. In October 2006, Plaintiff Maximo purchased his residence, funded in part by a promissory note secured by a deed of trust in favor of First Franklin, with MERS listed as the beneficiary. In February 2009, after Plaintiff Almendarez discontinued making payments on his note, Almendarez's residence was sold at a public auction. In August 2008, Maximo discontinued making payments on his promissory note. A Notice of Trustee's Sale was recorded with the Maricopa County Recorder on December 23, 2008. A public auction was to be held on March 24, 2009, concerning the sale of Maximo's residence. The public auction was rescheduled for April 24, 2009. On April 22, Maximo filed with this Court a Notice of Defendant's Cancellation of Trustee's Sale and Plaintiff's Request for Hearing on Preliminary Injunction (Doc. # 56). In his notice, Maximo related that the public auction scheduled for April 24 had been canceled. In light of this cancellation, this Court denied Maximo's request for a preliminary injunction. (Doc. # 185.) In March 2009, Plaintiffs collectively brought this present action, alleging violations of the Truth in Lending Act, Real Estate Settlement Procedures Act, Home Ownership and Equity Protection Act, Fair Housing Act, Arizona Consumer Fraud Act. Plaintiffs also seek damages from state law claims of conspiracy to commit fraud and conversion, as well as for intentional infliction of emotional distress. Lastly, Plaintiffs seek injunctive and declaratory relief. ANALYSIS Motions to Dismiss "A Rule 12(b)(6) motion to dismiss tests the legal sufficiency of a claim." Navarro v. Block, 250 F.3d 7129, 732 (9th Cir.2001). "To survive a motion to dismiss, a complaint must contain sufficient factual matter, accepted as true, to `state a claim to relief that is plausible on its face.'" Ashcroft v. Iqbal, 129 S.Ct. 1937, 1949 (2009) (quoting Bell Atl. -2- 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Corp. v. Twombly, 550 U.S. 544, 570 (2007)). "The plausibility standard is not akin to a `probability requirement,' but it asks for more than a sheer possibility that a defendant has acted unlawfully." Iqbal, 129 S.Ct. at 1949. "Where a complaint pleads facts that are `merely consistent with' a defendant's liability, it `stops short of the line between possibility and plausibility of entitlement to relief.' " Id. (quoting Twombly, 550 U.S. at 557). "While a complaint attacked by a Rule 12(b)(6) motion to dismiss does not need detailed factual allegations, a plaintiff's obligation to provide the grounds of entitlement to relief requires more than labels and conclusions, and a formulaic recitation of the elements of the cause of action will not do." Twombly, 550 U.S. at 545 (internal quotations, citations and alterations omitted). "Determining whether a complaint states a plausible claim for relief . . . [is] a context-specific task that requires the reviewing court to draw on its judicial experience and common sense. But where the well-pleaded facts do not permit the court to infer more than the mere possibility of misconduct, the complaint has alleged-but it has not `show[n]'-`that the pleader is entitled to relief.'" Iqbal, 129 S.Ct. at 1950 (quoting FED. RULE CIV. PROC. 8(a)(2)) (citation omitted).2 Count I In their first claim for relief, Plaintiffs allege various violations of the Truth in Lending Act ("TILA"), 15 U.S.C. �� 1601, et seq., including inadequate disclosures, improper charges, and failed notices. Defendants First Franklin and Countrywide Home Loans move to dismiss Plaintiffs' first cause of action for a failure to state a claim pursuant to Rule 12(b)(6), while Defendant National City Bank ("NCB") moves to dismiss Plaintiff's first cause of action for lack of standing. The Court will analyze standing first because "[s]tanding is the threshold issue of any federal action, a matter of jurisdiction because `the core component of standing is an essential and unchanging part of the case-or-controversy requirement of Article III.'" Local Nos. 175 Although there were various exhibits attached to certain motions to dismiss, responses, or replies, the Court makes clear that it did not consider anything beyond the complaint in deciding the motions to dismiss. -32 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 & 505 Pension Trust v. Anchor Cap., 498 F.3d 920, 923 (9th Cir. 2007) (quoting Lujan v. Defenders of Wildlife, 504 U.S. 555, 561 (1992)). In order to establish Article III standing, a plaintiff must demonstrate: "(1) it has suffered an `injury in fact' that is (a) concrete and particularized and (b) actual or imminent, not conjectural or hypothetical; (2) the injury is fairly traceable to the challenged action of the defendant; and (3) it is likely, as opposed to speculative, that the injury will be redressed by a favorable decision." Friends of the Earth, Inc. v. Laidlaw Envtl. Servs. (TOC), Inc., 528 U.S. 167, 180-81 (2000). Defendant NCB premises its argument that Plaintiffs lack standing to sue NCB on Plaintiffs not having been personally injured by NCB. That is, Plaintiffs' do not allege that they actually received a mortgage loan from NCB. Rather, Plaintiffs "seek to assign liability to NCB solely because First Franklin was a subsidiary of NCB." (Doc. # 128 at p. 8.) In response, Plaintiffs argue that NCB did in fact extend loans to Plaintiffs because Plaintiff Almendarez and Plaintiff Maximo's deeds of trust were executed in favor of "First Franklin, a Division of National City Bank." The Court concludes that Plaintiffs have failed to carry their burden demonstrating that they have standing to sue NCB under Counts I, II, and IV. Plaintiffs' have failed, both in their complaint and in their response to NCB's motion to dismiss, to demonstrate that NCB participated in the origination of any of Plaintiffs' loans. The only connection between Plaintiffs' loans and NCB is the phrase "First Franklin, a Division of National City Bank" contained in Plaintiffs Almendarez and Maximo's deeds of trust. Yet, even this phrase makes clear that the deeds of trust are being executed in favor of First Franklin. At most, this phrase in the deeds of trust demonstrates that First Franklin is a mere corporate relation of NCB. However, this is not the equivalent of NCB extending a loan to Plaintiffs, or otherwise participating in the loan origination process in violation of TILA. See Royal Indus. v. St. Regis Paper Co. 420 F.2d 449, 453 (9th Cir. 1969) ("The separate identities of a parent and its subsidiary, even a wholly owned subsidiary, will not be disregarded unless a recognition of their separateness, under the circumstances, would -4- 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 sanction a fraud or promote injustice."). Plaintiffs have failed to demonstrate that their alleged injuries are fairly traceable to NCB.3 The Court next addresses Defendants First Franklin and Countrywide's motion to dismiss pursuant to Rule 12(b)(6). Defendants argue that Plaintiffs' allegations contained in their first claim of relief are merely generalized allegations containing labels and conclusions and, as such, are insufficient under Twombly. The Court disagrees. While certain of Plaintiffs' allegations in Count I do contain formulaic recitation of the elements for TILA violations, Plaintiffs included a sufficient amount of factual allegations to survive a Rule 12(b)(6) motion. For example, Plaintiff Almendarez alleges that he was not provided with a final calculation of the interest rate, finance charges, or the annual percentage rates on the final amount of his mortgage. Moreover, Plaintiffs Almendarez and Maximo allege that they only speak Spanish and that none of the closing documents were translated into Spanish. Plaintiffs also assert that Defendants calculated the annual percentage rate based upon improperly disclosed amounts. Such allegations suffice for the Rule 12(b)(6) stage of the proceedings. However, Defendants also argue that Plaintiffs' allegations in Count I are time-barred under the applicable statute of limitations. In response, Plaintiffs assert that they sufficiently alleged equitable tolling such that the statute of limitations does not preclude their first claim for relief. The Court finds that the statute of limitations applies. A cause of action brought under TILA must be commenced "within one year from the date of the occurrence of the violation." 15 U.S.C. � 1640(e). Each Plaintiff obtained his or her loan in 2006. This present action was commenced in March of 2009. Hence, under section 1640(e), Plaintiffs' TILA claims are barred absent any applicable exclusions. The general rule is that the statute of limitations period commences at the consummation of the transaction. King v. California, 784 F.2d 910, 915 (9th Cir. 1986). Even if the Court concluded that Plaintiffs had standing to sue NCB, for the reasons stated later in this Order, Plaintiffs' claims against NCB would likewise be dismissed. -5- 3 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 However, "the doctrine of equitable tolling may, in the appropriate circumstances, suspend the limitations period until the borrower discovers or had reasonable opportunity to discover the fraud or nondisclosures that form the basis of the TILA action." Id. "Equitable estoppel, also termed fraudulent concealment, halts the statute of limitations when there is active conduct by a defendant, above and beyond the wrongdoing upon which the plaintiff's claim is filed, to prevent the plaintiff from suing in time." Guerrero v. Gates, 442 F.3d 697, 706 (9th Cir. 2006) (quotations omitted). Here, Plaintiffs allege that Defendants "fraudulently misrepresented and concealed the true facts related to the items subject to disclosure," and Plaintiffs "did not discover the Defendants' failure to make the disclosures pursuant to 15 U.S.C. � 1638 until one year within the filing of this complaint." (Doc. # 5 at p. 25, �� 96-97.) Such statements are the only allegations pertaining to equitable estoppel in Plaintiffs' complaint. Plaintiffs do not allege any facts supporting these legal conclusions, such as how Defendants fraudulently misrepresented or concealed the true facts, or why Plaintiffs were otherwise precluded from discovering the TILA violations at the consummation of their loans�the general rule for when the statute of limitations commences under section 1638. Such factual underpinnings are all the more important in such a case as the one before the Court since the vast majority of Plaintiffs' alleged violations under TILA are violations that are self-apparent at the consummation of the transaction�e.g., not being provided a notice of one's right to rescind the transaction at the time of closing, not being properly provided with the annual percentage rate, finance charges, total amount financed, payment schedule, etc. Plaintiffs' assertions pertaining to equitable estoppel are pure legal conclusions devoid of any supporting factual allegations. The Court finds that Plaintiffs have failed to adequately allege a claim for equitable tolling such that the one-year statute of limitation contained in 15 U.S.C. � 1638 should not apply. Accordingly, the Court applies the general rule under section 1638 and finds that Plaintiffs' claims under TILA are time-barred. /// /// -6- 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Count II In their second claim for relief, Plaintiffs allege violations of the Real Estate Settlement Procedures Act ("RESPA"), 12 U.S.C. �� 2601, et seq. Specifically, Plaintiffs allege that: Defendants failed to provide a uniform settlement statement and a special information booklet, including a good faith estimate of the amount of charges for settlement services; Defendants were required to inform Plaintiffs at the time of application for their loans whether the servicing of the loans could be sold or transferred and, if the loans were sold or transferred, Plaintiffs are entitled to 15 days notice before the sale or transfer; Defendants were prohibited from paying any fee, kickback, or thing of value as a part of the real estate settlement service involving the loans; Defendants were required to disclose any controlled business arrangements; and Defendants charged Plaintiffs with unreasonably high fees and charges for settlement services. The Court finds that Plaintiffs have not stated a viable claim for relief under count two. Plaintiffs' claims that Defendants violated RESPA by failing to provide a uniform settlement statement, a special information booklet, and a good faith estimate of the amount of charges for settlement services fail because there is no private cause of action for such alleged violations of RESPA. Bloom v. Martin, 865 F.Supp. 1377, 1383-85 (N.D.Cal.1994); Walker v. Artisan Mortgage, LLC, 2008 WL 2026365, * 3 (D. Ariz. 2008). Plaintiffs' next claim that Defendants were required to inform them whether the servicing of the loans could be sold or transferred, and if the loans were to be sold or transferred, Plaintiffs are entitled to 15 days notice before the sale or transfer, likewise fails. Under section 2605, which is the rubric of RESPA that Plaintiffs' allegations fall under, a plaintiff must allege actual damages resulting from a violation of section 2605. 12 U.S.C. � 2605(f)(1)(A) ("Whoever fails to comply with any provision of this section shall be liable to the borrower for each such failure in the following amounts: . . . In the case of any action by an individual, an amount equal to the sum of-- (A) any actual damages to the borrower as a result of the failure."); Collier v. Wells Fargo Home Mortg., 2006 WL 1464170, *3 (N.D.Tex. 2006); Hepler v. Washington Mut. Bank, F.A., 2009 WL 1045470, *4-5 (C.D.Cal. -7- 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 2009). Plaintiffs have failed to allege any such damages. As such, their claims under section 2605 fail. Plaintiffs' next allegation under Count II states that "Pursuant to 12 U.S.C. � 2607(a), Defendants were prohibited from paying any `fee, kickback, or thing of value' to any person as part of the real estate settlement service involving the loans described herein." (Doc. # 5 at p. 28, � 109.) Plaintiffs' allegation falls short of the Rule 12(b)(6) standard propounded by Twombly and Iqbal. Plaintiffs merely state that Defendants were prohibited from violating section 2607(a). Plaintiffs do not actually allege that Defendants violated section 2607(a) and, more importantly, Plaintiffs do not provide any facts supporting such an assertion. At most, Plaintiffs have provided a legal conclusion pertaining to 12 U.S.C. � 2607(a) and, as such, Plaintiffs' claim fails under a Rule 12(b)(6) motion. Similarly, Plaintiffs' claim that Defendants were required to disclose any "controlled business arrangements" fails under Twombly and Iqbal. (Doc. # 5 at p. 28, � 110.) Plaintiffs allege only a one-sentence legal conclusion, providing no facts in support of their allegation. Moreover, the Court is unable to discover where the phrase "controlled business arrangements" is found in 12 U.S.C. �� 2601 et seq. RESPA contains the phrase "affiliated business arrangement," yet Plaintiffs fail to allege to whom Defendants directly or indirectly improperly referred business. Nor do Plaintiffs allege that they were required to use such a provider within the context of section 2607. Accordingly, Plaintiffs' claim fails. Lastly under RESPA, Plaintiffs allege that Defendants charged unreasonably high fees and charges for settlement services. As several courts have recognized, however, RESPA was not intended to serve as a price cap for settlement services, and the text of RESPA does not support such an allegation. Maganallez v. Hilltop Lending Corp., 505 F.Supp.2d 594, 604, (N.D.Cal. 2007) (dismissing similar claim and collecting cases). Therefore, the Court finds that Plaintiffs have failed to allege a claim under RESPA for which relief may be granted and, as such, the Court dismisses Plaintiffs' claims under Count II. /// -8- 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Count III In her third claim for relief, Plaintiff Cervantes alleges a violation of the Home Ownership and Equity Protection Act ("HOEPA"), 15 U.S.C. �� 1602(aa), 1610, and 1639. However, in Plaintiffs' motion to amend their first amended complaint, Plaintiff Cervantes seeks to withdraw her HOEPA claim. (Doc. # 189 at pp. 1-2.) Thus, the Court need not address Plaintiff Cervantes' claims under HOEPA. Count IV In Plaintiffs' fourth claim for relief, they allege a violation of the Fair Housing Act ("FHA") 42 U.S.C. �� 3601, et seq. Specifically, Plaintiffs allege that Defendants offered Plaintiffs "a less-than-favorable loan" based upon Plaintiffs' race and that Defendants targeted Plaintiffs for predatory lending because of Plaintiffs race. (Doc. # 5 at p. 34, �� 13334.) In response, Defendants argue that Plaintiffs fail to state a cognizable claim for relief. The Court agrees with Defendants. In the discrimination context, a plaintiff must do more than simply allege a generalize discrimination. See Smith v. City of Jackson, Miss., 544 U.S. 228, 241 (2005) (stating in the employment discrimination context that "it is not enough to simply allege that there is a disparate impact on workers, or point to a generalized policy that leads to such an impact. Rather, the employee is responsible for isolating and identifying the specific employment practices that are allegedly responsible for any observed statistical disparities") (quotations omitted). Here, Plaintiffs allege nothing more than Defendants "purposefully targeted" Plaintiffs because of their race and Plaintiffs received "a less-than-favorable loan than would have been offered to a white borrower." (Doc. # 5 at p. 34, �� 133-34.) Such allegations, again, are mere legal conclusions. Plaintiffs do not allege any facts supporting such allegations�e.g., Plaintiffs were qualified for a better loan based upon objective indicators such as income and credit ratings, Defendants offered similarly situated borrowers outside of Plaintiffs' racial class more beneficial loan options, etc. Thus, the Court finds that Plaintiffs have failed to state a plausible claim for relief under FHA. -9- 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 In any event, Plaintiffs' claims under Count IV are time-barred. Discrimination claims under FHA have a two-year statute of limitations time period. 42 U.S.C. � 3613 (a)(1)(A) ("An aggrieved person may commence a civil action in an appropriate United States district court or State court not later than 2 years after the occurrence or the termination of an alleged discriminatory housing practice."). As described in the discussion under Count I, Plaintiffs obtained their loans in 2006 and brought this present action in March 2009. As such, Plaintiffs' claims fall outside the two-year time limitation. Nevertheless, Plaintiffs allege a continuing violation theory. Under the continuing violation theory, when "a plaintiff, pursuant to the Fair Housing Act, challenges not just one incident of conduct violative of the Act, but an unlawful practice that continues into the limitations period, the complaint is timely when it is filed within . . . the last asserted occurrence of that practice." Havens Realty Corp. v. Coleman, 455 U.S. 363, 380-81 (1982). However, "[a] continuing violation is occasioned by continual unlawful acts, not by continual ill effects from an original violation." Ward v. Caulk, 650 F.2d 1144, 1147 (9th Cir.1981). The Court finds that Defendants' issuing of the loans in question were one-time acts. Even if the Court assumed that Defendants' actions violated the FHA, the discriminatory act took place at the time Defendants extended the loan to Plaintiffs. Therefore, because Plaintiffs filed their action under FHA more than two-years after the alleged discriminatory acts, Plaintiffs' FHA claims are time-barred.4 Count V In their fifth claim for relief, Plaintiffs argue that Defendants violated the Arizona Consumer Fraud Act ("ACFA"), Arizona Revised Statutes ("A.R.S.") section 44-1522, et seq., by using "deception, false promises, and misrepresentation regarding the terms of the Plaintiffs' allegation that "Defendants have engaged in a pattern or extended practice of exploiting the market of Hispanics in the market area where Plaintiffs reside" (Doc. # 5 at p. 35, � 137) is a mere legal conclusion unsupported by any factual allegations and, as such, is not a plausible claim for a continuing violation under the standards enunciated by Twombly or Iqbal. - 10 - 4 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 loan offered to" Plaintiffs. Defendants argue that Plaintiffs' claims under Count V are timebarred and, in any event, they fail to state a claim under Rule 12(b)(6). The Court need not reach Defendants' latter argument, as the Court finds that Plaintiffs' claims under Count V are barred by the applicable statute of limitations. Actions commenced pursuant to A.R.S. � 44-1522 must be brought within one year. A.R.S. � 12-541(5) (2003) ("There shall be commenced and prosecuted within one year after the cause of action accrues, and not afterward, the following actions: . . . Upon a liability created by statute, other than a penalty or forfeiture."). An action accrues under ACFA "when the defrauded party discovers or with reasonable diligence could have discovered the fraud." Alaface v. Nat'l Inv. Co., 892 P.2d 1375, 1379 (Ariz. Ct. App. 1994) (quoting Mister Donut of Am., Inc. v. Harris, 723 P.2d 670, 672 (1986)). Put another way, a cause of action under ACFA "accrues when `the plaintiff knows or should have known of both the what and who elements of causation.'" Alaface, 892 P.2d at 1379 (quoting Lawhon v. L.B.J. Institutional Supply, Inc.,765 P.2d 1003, 1007 (App.1988)). Here, as described in the discussion under Count I, Plaintiffs obtained their loans in 2006 and brought this present action in March 2009. The who of Plaintiffs' cause of action under ACFA was known at the time Plaintiffs obtained their loans, as Plaintiffs' make no allegations to the contrary and the named Defendants under Count V are the very Defendants Plaintiffs allege are responsible for the origination of their loans. Plaintiffs allege, however, that they "learned of Defendants' violation of A.R.S. � 44-1522 within one year of the filing of this complaint." (Doc. # 5 at p. 37, � 145.) Thus, Plaintiffs allege that their cause of action accrued within one year of the filing of their complaint because they did not know the what element of their ACFA claim. However, the test for when a cause of action accrues is not only what the plaintiff actually knew, but what he or she should have known or could have discovered with reasonable diligence. Alaface, 892 P.2d at 1379. Plaintiffs allegations under ACFA, even when assumed to be true, are all related to facts that were discoverable at the time Plaintiffs entered into their loan transactions. The allegations revolve around the very terms of the loans, such as interest rate, payments to be - 11 - 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 made under the loan, and Plaintiffs' ability to refinance. Plaintiffs do not allege that the terms Defendants seek to enforce are different or somehow an alteration from the promissory notes Plaintiffs signed. Rather, Plaintiffs' allegations amount to a claim that the terms contained in the promissory notes are material deviations from the terms Plaintiffs were promised before entering into the loan transactions. Even assuming there are material deviations to support a claim under ACFA, the "what element of causation" was apparent at the time Plaintiffs entered into the loan transactions�Plaintiffs could have discovered the deviations in the documents they were signing. Accordingly, Plaintiffs' ACFA cause of action accrued upon entering their loan transactions and are therefore precluded under A.R.S. � 12-541(5). Count VI In their sixth claim for relief, Plaintiffs allege that Defendants Countrywide, NCB, First Franklin, and Mortgage Electronic Registration Systems, Inc. ("MERS") conspired to commit both fraud and conversion. Defendants respond that Plaintiffs have failed to state a claim for civil conspiracy. In Arizona, there is no independent tort of conspiracy. Hansen v. Stoll, 636 P.2d 1236, 1242 (Ariz. Ct. App. 1981). "A civil conspiracy requires an underlying tort which the alleged conspirators agreed to commit." Baker ex rel. Hall Brake Supply, Inc. v. Stewart Title & Trust of Phoenix, Inc., 5 P.3d 249, 259 (Ariz. Ct. App. 2000). In this case, Plaintiffs allege underlying torts of fraud and conversion. "Arizona has adopted the following definition of conversion . . . `Conversion is an intentional exercise of dominion or control over a chattel which so seriously interferes with the right of another to control it that the actor may justly be required to pay the other the full value of the chattel.'" Miller v. Hehlen, 104 P.3d 193, 203 (Ariz. Ct. App. 2005) (quoting RESTATEMENT (SECOND) OF TORTS � 222A(1) (1965)) (emphasis added). "`An action for conversion ordinarily lies only for personal property that is tangible, or to intangible property that is merged in, or identified with, some document.'" Miller, 104 P.3d at 203 (quoting 18 Am.Jur.2d, Conversion � 7 (2004)). Plaintiffs allegations amount to conversion not of chattel - 12 - 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 or personal property, but real property.5 However, there is no tort of conversion of real property in Arizona. See Strawberry Water Co. v. Paulsen, 207 P.3d 654, 659 (Ariz. Ct. App. 2008) (distinguishing different types of water types and stating that "[w]ater rights are real property interests, and thus cannot be converted because they are not chattels.") (citations omitted). Moreover, even if Plaintiffs' claims do involve "chattel," Plaintiffs have failed to allege how Defendants exercised dominion or control in such a manner that Plaintiffs did not have the right to control the chattel. Accordingly, the Court finds that Plaintiffs' claim for conspiracy based upon conversion fails to state a claim upon which relief may be granted. Regardless of the merits of Plaintiffs' underlying claims for fraud and conversion, Plaintiffs' claim that Defendants conspired to commit fraud and conversion is insufficient both for a failure to plead conspiracy with the requisite particularity and for a failure to plead an agreement to participate in the fraud and conversion. "In alleging fraud or mistake, a party must state with particularity the circumstances constituting fraud or mistake." FED. R. CIV. P. 9(b). Plaintiffs allegations with respect to fraud were not made with particularity. Rather, Plaintiffs' allegations amount to mere conclusory statements and general averments of fraud. Plaintiffs allege that Defendants: formed an association to conspire in order to deprive Plaintiffs of their property; knew Plaintiffs would be unable to pay the loans and, thus, Defendants would be in a position to seize Plaintiffs' real property through foreclosure; and targeted Plaintiffs for the purpose of misrepresenting the terms of the loans in order to seize 5 Plaintiffs argue in their response to Defendants' motion to dismiss that they have "stated a claim for conversion in that Plaintiffs had a right to be free from illegal foreclosures, and a right to the full disclosures mandated by federal law." (Doc. # 156 at p. 14.) However, Plaintiffs fail to cite any Arizona cases recognizing an action for conversion based upon an illegal foreclosure or for incomplete disclosures. Moreover, the Court fails to see how the right to be free from an illegal foreclosure (or an incomplete disclosure) is not related and integral to Plaintiffs' real property rights in the said properties. Stated another way, the Court does not believe that Plaintiffs' right to be free from an illegal foreclosure can properly be divorced from Plaintiffs' real property rights. - 13 - 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Plaintiffs' properties. Plaintiffs also repeat their allegations that Defendants violated TILA, RESPA, HOEPA, ACFA, and the Fair Housing Act. Plaintiffs do not allege that Defendants entered into an express agreement to commit fraud and conversion. Rather, Plaintiffs allege that Defendants "formed an association to conspire." (Doc. # 5 at p. 38 at � 148.) "[A] plaintiff must allege with sufficient factual particularity that defendants reached some explicit or tacit understanding or agreement. It is not enough to show that defendants might have had a common goal unless there is a factually specific allegation that they directed themselves towards this wrongful goal by virtue of a mutual understanding or agreement." S. Union Co. v. Sw. Gas Corp., 165 F.Supp.2d 1010, 1020-21 (D. Ariz. 2001) (quoting Alfus v. Pyramid Technology Corp., 745 F.Supp. 1511, 1521 (N.D. Cal. 1990)). Plaintiffs have not stated how or even when the alleged conspiracy was formed. Plaintiffs have also not included any factual allegations pertaining to how Defendants targeted Plaintiffs. Plaintiffs' allegations amount to a claim that Defendants somehow formed a conspiracy with the intent to provide Plaintiffs with a loan, the terms of which they could not afford, thus permitting Defendants to gain control of the properties through foreclosure. "But terms like `conspiracy,' or even `agreement,' are border-line: they might well be sufficient in conjunction with a more specific allegation�for example, identifying a written agreement or even a basis for inferring a tacit agreement�but a court is not required to accept such terms as a sufficient basis for a complaint. The case law on this point is ample." DM Research, Inc. v. Coll. of Am. Pathologists, 170 F.3d 53, 56 (1st Cir. 1999) (cited with approval in Twombly, 550 U.S. at 557). Plaintiffs have failed to provide any specific, factual allegations inferring even a tacit agreement. As such, Plaintiffs sixth claim for relief falls short of the requirements of Rule 9(b), Twombly, and Iqbal. Count VII In their seventh claim for relief, Plaintiffs assert that the various named Defendants that are members of the MERS system, conspired to commit fraud through the MERS system. In response, Defendants filed several motions to dismiss raising similar arguments under Rules 9(b) and 12(b)(6), as well as joining in the motions to dismiss of other named - 14 - 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Defendants. The Court need not reiterate each of the arguments, as Plaintiffs have failed to state a viable claim for relief for conspiracy to commit fraud under Rule 12(b)(6). At its core, Plaintiffs' claim for conspiracy to commit fraud is an attack on the MERS system. However, because Plaintiffs claim that the MERS system is a fraud fails as a matter of law, Plaintiffs' claim for conspiracy to commit fraud based upon the MERS system likewise must fail. MERS is a wholly owned subsidiary of MERSCORP, a Virginia corporation. Various of the named Defendant banks and lending institutions are shareholders in MERSCORP and participants in the MERS system. Under the MERS system, at the origination of a residential loan, the lender takes possession of a promissory note and the borrower and lender agree to designate MERS as the beneficiary under a deed of trust. Under the MERS system, the rights to the mortgage are tracked internally and not recorded in the public records each time the rights to the mortgage are bought and sold, so long as the buyer is a member of the MERS system. Plaintiffs' complaints from this system are two-fold: (1) MERS is never really a beneficiary under the deed of trust because it never acquires a true beneficial interest; and (2) the MERS system is a means of circumventing the public recording requirements. In support of its first objection, Plaintiffs allege that MERS never owns or acquires any beneficial interest in any of the loans it is named as the beneficiary under a deed of trust. As such, Plaintiffs allege that the MERS system is a "sham" beneficiary. Plaintiffs, however, have not directed this Court to any Arizona case that finds that the MERS system is fraudulent. Indeed, Plaintiffs' allegations would foreclose the very splitting of a promissory note from a deed of trust. Such an approach, of course, would intrude into the realm of thirdparty beneficiary contracts, as well as assignments and delegations. More importantly, Plaintiffs have failed to allege what effect, if any, listing the MERS system as a "sham" beneficiary on the deed of trust had upon their obligations as borrowers. The members of the MERS system were not participants in Plaintiffs' loan origination process, nor do Plaintiffs so allege. Plaintiffs do not allege that they were somehow induced to enter into their loans on the basis that MERS was a genuine and not a "sham" beneficiary. - 15 - 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Moreover, the Court fails to see how the MERS system commits a fraud upon Plaintiffs. Plaintiffs' argument that MERS is a "sham" beneficiary is unconvincing. Otherwise, any situation where a beneficiary obtains less than the full rights possessed by the entity or person granting the beneficiary status would likewise result in a "sham" beneficiary. The fact that MERS does not obtain such rights as to collect mortgage payments or obtain legal title to the property in the even of non-payment does not transform MERS' status into a "sham." Plaintiffs second objection to the MERS system similarly has no effect upon their status as borrowers. The original mortgage between the borrower and the lender, which lists MERS as the beneficiary, is recorded in the public land records. Subsequent sales of the mortgage, so long as they involve MERS members, are not recorded in the public records but, rather, are tracked in the MERS system. Thus, Plaintiffs really attack the notice, or lack thereof, to future buyers of mortgages in the MERS system. Any lack of notice in the public records, however, to future buyers of Plaintiffs' mortgages does not alter Plaintiffs' obligations under the mortgages; nor have Plaintiffs alleged that, had they been fully apprised of the MERS system and its use of an in-house records keeping system, Plaintiffs would not have entered into their loans. Plaintiffs also do not allege that they were somehow induced into entering into their loans based upon a misunderstanding of the MERS system. For these reasons, the Court finds that Plaintiffs' claim for conspiracy to commit fraud fails as a matter of law under Rule 12(b)(6). In Arizona, a fraud claim requires proof of nine elements: (1) a representation; (2) its falsity; (3) its materiality; (4) the speaker's knowledge of its falsity or ignorance of its truth; (5) the speaker's intent that it be acted upon by the recipient in a manner reasonably contemplated; (6) the hearer's ignorance of the falsity of the representation; (7) the hearer's reliance on the truth of the representation; (8) the right to rely on it; and (9) consequent and proximate injury. Echols v. Beauty Built Homes, Inc., 647 P.2d 629, 631 (1982). The Court finds that elements two, three, seven, and nine are all absent from Plaintiffs' complaint. For the reasons articulated above, the Court finds that Defendants representations to Plaintiffs that MERS would serve as the beneficiary under the - 16 - 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 deed of trust was not a false representation and, even if such a representation was false, the Court finds that it was not material. Furthermore, Plaintiffs have failed to adequately allege that Defendants' representations concerning the MERS system�including serving as the beneficiary under the deeds of trust�induced them to rely upon such representations and, in so doing, Plaintiffs have suffered injuries that resulted from the false representations. At most, Plaintiffs find the MERS system to be disagreeable and inconvenient to them as consumers. Such complaints, however, do not arise to the level of fraud, much less a conspiracy to commit fraud. Count VIII In their eighth claim for relief, Plaintiffs seek damages for Defendants' intentional infliction of emotional distress. To prove a claim of intentional infliction of emotional distress under Arizona law, Plaintiffs must show that: 1) Defendants engaged in extreme and outrageous conduct; 2) Defendants either intended to cause emotional distress or recklessly disregarded the near certainty that emotional distress would result from the conduct; and 3) Plaintiffs actually suffered emotional distress because of Defendants' conduct. Watts v. Golden Age Nursing Home, 619 P.2d 1032, 1035 (Ariz. 1980). "To establish a claim under this tort, the conduct alleged must be `atrocious' and `beyond all possible bounds of decency' so that an average member of the community would regard it as outrageous. Lucchesi v. Stimmell, 716 P.2d 1013, 1015 (Ariz. 1986). "It is for the court to determine, in the first instance, whether the defendant's conduct may reasonably be regarded as so extreme and outrageous as to permit recovery, or whether it is necessarily so." Id. at 1016 (quoting RESTATEMENT (SECOND) OF TORTS � 46 (1965)). Plaintiffs' allegations that Defendants targeted Plaintiffs because of their vulnerability to Defendants' alleged predatory lending practices, even if true, do not arise to the level of "atrocious," and do not go "beyond all possible bounds of decency." Further, it is not enough that Defendants acted with an intent that is tortious or even criminal. RESTATEMENT (SECOND) OF TORTS � 46 cmt. d. Plaintiffs' allegations fail to state a claim for relief under Arizona law for intentional infliction of emotional distress, as the alleged conduct is not the - 17 - 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 type of conduct that "falls at the very extreme edge of the spectrum of possible conduct." Watts, 619 P.2d at 1035. Counts IX & X In their ninth and tenth claims for relief, Plaintiffs seek injunctive and declaratory relief, respectively. However, for the various reasons discussed above, the Court has already found that Plaintiffs' claims contained in Counts I-VIII must be dismissed. Therefore, any request for injunctive and declaratory relief premised upon Counts I-VIII must likewise fail. A.R.S. � 33-807 In addition to the arguments raised by the other Defendants, which are addressed above, Defendant Tiffany & Bosco, P.A. argues that Arizona Revised Statutes section 33807(E) (2007) precludes the filing of such actions against T&B as trustee. In response, Plaintiffs argue that T&B were not properly appointed as trustee and T&B failed to act in good faith. Section 33-807(E) provides: The trustee need only be joined as a party in legal actions pertaining to a breach of the trustee's obligation under this chapter or under the deed of trust. Any order of the court entered against the beneficiary is binding upon the trustee with respect to any actions that the trustee is authorized to take by the trust deed or by this chapter. If the trustee is joined as a party in any other action, the trustee is entitled to be immediately dismissed and to recover costs and reasonable attorney fees from the person joining the trustee. (Emphasis added.) T&B was substituted as trustee on the Almandarez and Maximo deeds of trust.6 The Court disagrees that T&B was not properly appointed as trustee. Plaintiffs do not argue that, procedurally, T&B was improperly added as substitute trustee, nor that, but for being appointed by MERS, T&B is not otherwise permitted under Arizona law to act in the capacity as a trustee. Rather, Plaintiffs' contention is that MERS has no authority to appoint a trustee and, thus, T&B's appointment is a nullity. However, as discussed above, the Court T&B argues that only Michael A. Bosco, Jr., was appointed as the substitute trustee and not T&B. However, the Court need not resolve this dispute as the Court finds that T&B was improperly named in this suit under A.R.S. � 33-807(E). - 18 - 6 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 rejects Plaintiffs' argument that the MERS system is a fraud and is without authority to act as a beneficiary under a deed of trust. Likewise, the Court rejects Plaintiffs' argument that T&B did not act in good faith. Plaintiffs' argument is merely a corollary of its argument that T&B was not duly appointed. That is, Plaintiffs argue that because T&B was added as trustee by MERS�who has no authority to appoint a trustee�T&B's actions as trustee�including foreclosure actions�were not conducted in good faith since T&B failed to adequately investigate whether they were lawfully appointed as trustee. However, because the Court rejects Plaintiffs' arguments related to the MERS system, the Court finds that Plaintiffs' complaint fails to state a claim that T&B did not act in good faith. T&B has requested its attorneys' fees and court costs for having to defend against Plaintiffs' action. Section 33-807(E) provides that "If the trustee is joined as a party in any other action, the trustee is entitled to be immediately dismissed and to recover costs and reasonable attorney fees from the person joining the trustee." (Emphasis added.) T&B may file a motion for attorneys fees and costs in accordance with LRCiv. 54.2. Motion To Amend Plaintiffs also seek leave of this Court to file a second amended complaint. Leave to amend a complaint is within the Court's sound discretion, and in exercising this discretion, the Court must be guided by the command of Rule 15(a), which provides that "leave shall be freely given when justice so requires." Allen v. City of Beverly Hills, 911 F.2d 367, 373 (9th Cir. 1990) (citing Fed.R.Civ.P. 15(a)). The Court should consider five factors when assessing whether to allow leave to amend: (1) bad faith, (2) undue delay, (3) prejudice to the opposing party, (4) futility of amendment, and (5) whether the plaintiff has previously amended the complaint. Id. When dismissing for failure to state a claim, the Court should grant leave to amend unless the Court determines that the pleading could not possibly be cured by the allegations of other facts. Doe v. United States, 58 F.3d 494, 497 (9th Cir. 1995); Bonin v. Calderon, 59 F.3d 815, 845 (9th Cir. 1995) ("Futility of amendment can, by itself, justify the denial of a motion for leave to amend."). - 19 - 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Plaintiffs attached their proposed second amended complaint as an exhibit to their motion to amend. The Court finds that Plaintiffs' request for a second amendment to their complaint was not done in bad faith, nor has it resulted from undue delay. Given that there have been several motions to dismiss filed on the basis of Plaintiffs' first amended complaint, the Court does find that there would be some level of prejudice to Defendants, albeit small. The Court also notes that Plaintiffs have already amended their complaint and are seeking leave to do so a second time. However, after reviewing Plaintiffs' second amended complaint, the Court finds that factor four�futility�weighs heavily against granting Plaintiffs' request for leave to amend. None of Plaintiffs' proposed changes in their second amended complaint rescue Plaintiffs' claims that are time-barred as discussed above. The thrust of Plaintiffs' changes occur in Count VII (or renumbered as Count VI in Plaintiffs' proposed second amended complaint). While Plaintiffs' proposed changes in Count VII do add details about the MERS system, they do not cure the deficiencies discussed above. Therefore, because the Court finds that Plaintiffs' request for a second amended complaint would prove futile, the Court denies the motion. CONCLUSION Accordingly, IT IS ORDERED that: Defendant Tiffany & Bosco, P.A.'s Motion to Dismiss is granted (Doc. # 44); Defendant GMAC Mortgage, L.L.C.'s Motion to Dismiss Plaintiffs' First Amended Complaint (Doc. # 118) is granted; Defendants MERS and MERSCORP, Inc.'s Motion to Dismiss (Doc. # 122) is granted; Defendants Freddie mac and Fannie Mae's Motion to Dismiss (Doc. # 123) is granted; Defendant United Guaranty Corporation's Motion to Dismiss (Doc. # 124) is granted; Defendants National City Corporation and PNC Financial Services Group, Inc.'s Motion to Dismiss (Doc. # 126) is granted; Defendant GE Money Bank's Motion to Dismiss (Doc. # 127) is granted; Defendants National City Bank and National City Mortgage's Motion to Dismiss (Doc. # 128) is granted; Defendants Countrywide and First Franklin's Motion to Dismiss (Doc. # 133) is granted; Defendant Wells Fargo's Motion to Dismiss (Doc. # 137) is granted; Defendant HSBC Mortgage - 20 - 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Corporations, U.S.A.'s Motion to Dismiss (Doc. # 139) is granted; Defendant JPMorgan Chase Bank, N.A.'s Motion to Dismiss (Doc. # 147) is granted. IT IS FURTHER ORDERED that Defendants Countrywide Home Loans, Inc., Bank of America, N.A., Merrill Lynch & Company, Inc., First Franklin Financial Corporation, and LaSalle Bank, N.A.'s Motion for Leave to File Sur-Reply (Doc. # 166) is denied as moot. IT IS FURTHER ORDERED that Plaintiffs Olga Cervantes, Carlos Almendarez, and Arturo Maximo's Motion to Amend Complaint (Doc. # 189) is denied. IT IS FURTHER ORDERED that Defendants' Motion to Transfer and Consolidate (Doc. # 194) is denied as moot. IT IS FURTHER ORDERED that Defendant Tiffany & Bosco, P.A.'s request for attorneys' fees is denied without prejudice, with leave to re-file pursuant to LRCiv 54.2. IT IS FINALLY ORDERED that the Clerk of the Court shall enter judgment accordingly. DATED this 23rd day of September, 2009. - 21 -

redpajama_set_name: RedPajamaCommonCrawl


text:
"""
A custom manager for working with trees of objects.
"""
from django.db import connection, models, transaction
from django.db.models import F, Max
from django.utils.translation import ugettext as _

try:
    from django.db import connections, router
except ImportError:
    # multi db support was new in django 1.2
    # NOTE we don't support django 1.1 anymore, so this stuff is likely to get removed soon
    connections = None
    router = None

from mptt.exceptions import InvalidMove
from mptt.utils import _exists

__all__ = ('TreeManager',)

qn = connection.ops.quote_name

COUNT_SUBQUERY = """(
    SELECT COUNT(*)
    FROM %(rel_table)s
    WHERE %(mptt_fk)s = %(mptt_table)s.%(mptt_pk)s
)"""

CUMULATIVE_COUNT_SUBQUERY = """(
    SELECT COUNT(*)
    FROM %(rel_table)s
    WHERE %(mptt_fk)s IN
    (
        SELECT m2.%(mptt_pk)s
        FROM %(mptt_table)s m2
        WHERE m2.%(tree_id)s = %(mptt_table)s.%(tree_id)s
          AND m2.%(left)s BETWEEN %(mptt_table)s.%(left)s
                              AND %(mptt_table)s.%(right)s
    )
)"""

class TreeManager(models.Manager):
    """
    A manager for working with trees of objects.
    """

    def init_from_model(self, model, prefix=None):
        """
        Sets things up. This would normally be done in contribute_to_class(),
        but Django calls that before we've created our extra tree fields on the
        model (which we need). So it's done here instead, after field setup.
        """

        self.prefix = prefix

        # Avoid calling "get_field_by_name()", which populates the related
        # model's cache and can cause circular imports in complex projects.
        # Instead, find the tree_id field using "get_fields_with_model()".
        [tree_field] = [fld for fld in model._meta.get_fields_with_model()
            if fld[0].name == self.get_tree_id_attr()]
        if tree_field[1]:
            # tree_model is the model that contains the tree fields.
            # this is usually just the same as model, but not for derived models.
            self.tree_model = tree_field[1]
        else:
            self.tree_model = model

        self._base_manager = None
        if self.tree_model is not model:
            # _base_manager is the treemanager on tree_model
            if self.prefix is None:
                tree_manager_name = '_tree_manager'
            else:
                tree_manager_name = '_%s_tree_manager' % self.prefix
            self._base_manager = getattr(self.tree_model, tree_manager_name)

    def get_parent_attr(self):
        return self.model._mptt_meta.get_parent_attr(prefix=self.prefix)

    @property
    def parent_attr(self):
        return self.get_parent_attr()

    def get_left_attr(self):
        return self.model._mptt_meta.get_left_attr(prefix=self.prefix)

    @property
    def left_attr(self):
        return self.get_left_attr()

    def get_right_attr(self):
        return self.model._mptt_meta.get_right_attr(prefix=self.prefix)

    @property
    def right_attr(self):
        return self.get_right_attr()

    def get_tree_id_attr(self):
        return self.model._mptt_meta.get_tree_id_attr(prefix=self.prefix)

    @property
    def tree_id_attr(self):
        return self.get_tree_id_attr()

    def get_level_attr(self):
        return self.model._mptt_meta.get_level_attr(prefix=self.prefix)

    @property
    def level_attr(self):
        return self.get_level_attr()

    def _translate_lookups(self, **lookups):
        new_lookups = {}
        for k, v in lookups.items():
            parts = k.split('__')
            new_parts = []
            for part in parts:
                new_parts.append(getattr(self, '%s_attr' % part, part))
            new_lookups['__'.join(new_parts)] = v
        return new_lookups

    def _mptt_filter(self, qs=None, **filters):
        """
        Like self.filter(), but translates name-agnostic filters for MPTT fields.
        """
        if self._base_manager:
            return self._base_manager._mptt_filter(qs=qs, **filters)

        if qs is None:
            qs = self.get_query_set()
        return qs.filter(**self._translate_lookups(**filters))

    def _mptt_update(self, qs=None, **items):
        """
        Like self.update(), but translates name-agnostic MPTT fields.
        """
        if self._base_manager:
            return self._base_manager._mptt_update(qs=qs, **items)

        if qs is None:
            qs = self.get_query_set()
        return qs.update(**self._translate_lookups(**items))

    def _get_connection(self, node):
        if connections is None:
            return connection
        else:
            return connections[router.db_for_write(node)]

    def add_related_count(self, queryset, rel_model, rel_field, count_attr,
                          cumulative=False):
        """
        Adds a related item count to a given ``QuerySet`` using its
        ``extra`` method, for a ``Model`` class which has a relation to
        this ``Manager``'s ``Model`` class.

        Arguments:

        ``rel_model``
           A ``Model`` class which has a relation to this `Manager``'s
           ``Model`` class.

        ``rel_field``
           The name of the field in ``rel_model`` which holds the
           relation.

        ``count_attr``
           The name of an attribute which should be added to each item in
           this ``QuerySet``, containing a count of how many instances
           of ``rel_model`` are related to it through ``rel_field``.

        ``cumulative``
           If ``True``, the count will be for each item and all of its
           descendants, otherwise it will be for each item itself.
        """
        meta = self.model._meta
        if cumulative:
            subquery = CUMULATIVE_COUNT_SUBQUERY % {
                'rel_table': qn(rel_model._meta.db_table),
                'mptt_fk': qn(rel_model._meta.get_field(rel_field).column),
                'mptt_table': qn(self.tree_model._meta.db_table),
                'mptt_pk': qn(meta.pk.column),
                'tree_id': qn(meta.get_field(self.get_tree_id_attr(
                    )).column),
                'left': qn(meta.get_field(self.get_left_attr(
                    )).column),
                'right': qn(meta.get_field(self.get_right_attr(
                    )).column),
            }
        else:
            subquery = COUNT_SUBQUERY % {
                'rel_table': qn(rel_model._meta.db_table),
                'mptt_fk': qn(rel_model._meta.get_field(rel_field).column),
                'mptt_table': qn(self.tree_model._meta.db_table),
                'mptt_pk': qn(meta.pk.column),
            }
        return queryset.extra(select={count_attr: subquery})

    def get_query_set(self):
        """
        Returns a ``QuerySet`` which contains all tree items, ordered in
        such a way that that root nodes appear in tree id order and
        their subtrees appear in depth-first order.
        """
        return super(TreeManager, self).get_query_set().order_by(
            self.get_tree_id_attr(),
                self.get_left_attr())

    def insert_node(self, node, target, position='last-child', save=False,
            allow_existing_pk=False):
        """
        Sets up the tree state for ``node`` (which has not yet been
        inserted into in the database) so it will be positioned relative
        to a given ``target`` node as specified by ``position`` (when
        appropriate) it is inserted, with any neccessary space already
        having been made for it.

        A ``target`` of ``None`` indicates that ``node`` should be
        the last root node.

        If ``save`` is ``True``, ``node``'s ``save()`` method will be
        called before it is returned.

        NOTE: This is a low-level method; it does NOT respect ``MPTTMeta.order_insertion_by``.
        In most cases you should just set the node's parent and let mptt call this during save.
        """

        if self._base_manager:
            return self._base_manager.insert_node(node, target, position=position, save=save)

        if node.pk and not allow_existing_pk and _exists(self.filter(pk=node.pk)):
            raise ValueError(_('Cannot insert a node which has already been saved.'))

        if target is None:
            setattr(node, self.get_left_attr(), 1)
            setattr(node, self.get_right_attr(), 2)
            setattr(node, self.get_level_attr(), 0)
            setattr(node, self.get_tree_id_attr(), self._get_next_tree_id())
            setattr(node, self.get_parent_attr(), None)
        elif target.is_root_node() and position in ['left', 'right']:
            target_tree_id = getattr(target, self.get_tree_id_attr())
            if position == 'left':
                tree_id = target_tree_id
                space_target = target_tree_id - 1
            else:
                tree_id = target_tree_id + 1
                space_target = target_tree_id

            self._create_tree_space(space_target, )

            setattr(node, self.get_left_attr(), 1)
            setattr(node, self.get_right_attr(), 2)
            setattr(node, self.get_level_attr(), 0)
            setattr(node, self.get_tree_id_attr(), tree_id)
            setattr(node, self.get_parent_attr(), None)
        else:
            setattr(node, self.get_left_attr(), 0)
            setattr(node, self.get_level_attr(), 0)

            space_target, level, left, parent, right_shift = \
                self._calculate_inter_tree_move_values(node, target, position,
                    )
            tree_id = getattr(parent, self.get_tree_id_attr())

            self._create_space(2, space_target, tree_id)

            setattr(node, self.get_left_attr(), -left)
            setattr(node, self.get_right_attr(), -left + 1)
            setattr(node, self.get_level_attr(), -level)
            setattr(node, self.get_tree_id_attr(), tree_id)
            setattr(node, self.get_parent_attr(), parent)

            if parent:
                self._post_insert_update_cached_parent_right(parent, right_shift,
                    )

        if save:
            node.save()
        return node

    def move_node(self, node, target, position='last-child'):
        """
        Moves ``node`` relative to a given ``target`` node as specified
        by ``position`` (when appropriate), by examining both nodes and
        calling the appropriate method to perform the move.

        A ``target`` of ``None`` indicates that ``node`` should be
        turned into a root node.

        Valid values for ``position`` are ``'first-child'``,
        ``'last-child'``, ``'left'`` or ``'right'``.

        ``node`` will be modified to reflect its new tree state in the
        database.

        This method explicitly checks for ``node`` being made a sibling
        of a root node, as this is a special case due to our use of tree
        ids to order root nodes.

        NOTE: This is a low-level method; it does NOT respect ``MPTTMeta.order_insertion_by``.
        In most cases you should just move the node yourself by setting node.parent.
        """

        if self._base_manager:
            return self._base_manager.move_node(node, target,
                position=position, )

        if target is None:
            if node.is_child_node():
                self._make_child_root_node(node, )
        elif target.is_root_node() and position in ['left', 'right']:
            self._make_sibling_of_root_node(node, target, position,)
        else:
            if node.is_root_node():
                self._move_root_node(node, target, position)
            else:
                self._move_child_node(node, target, position)
        transaction.commit_unless_managed()

    def root_node(self, tree_id):
        """
        Returns the root node of the tree with the given id.
        """
        if self._base_manager:
            return self._base_manager.root_node(tree_id)

        return self._mptt_filter(tree_id=tree_id, parent__isnull=True).get()

    def root_nodes(self):
        """
        Creates a ``QuerySet`` containing root nodes.
        """
        if self._base_manager:
            return self._base_manager.root_nodes()

        return self._mptt_filter(parent__isnull=True)

    def rebuild(self):
        """
        Rebuilds whole tree in database using `parent` link.
        """

        if self._base_manager:
            return self._base_manager.rebuild()

        opts = self.model._mptt_meta

        qs = self._mptt_filter(parent__isnull=True)
        if opts.order_insertion_by:
            qs = qs.order_by(*opts.order_insertion_by)
        pks = qs.values_list('pk', flat=True)

        idx = 0
        for pk in pks:
            idx += 1
            self._rebuild_helper(pk, 1, idx)

    def _post_insert_update_cached_parent_right(self, instance, right_shift):
        setattr(instance, self.get_right_attr(),
            getattr(instance, self.get_right_attr()) + right_shift)
        attr = '_%s_cache' % self.get_parent_attr()
        if hasattr(instance, attr):
            parent = getattr(instance, attr)
            if parent:
                self._post_insert_update_cached_parent_right(parent, right_shift,
                    )

    def _rebuild_helper(self, pk, left, tree_id, level=0):
        opts = self.model._mptt_meta
        right = left + 1

        qs = self._mptt_filter(parent__pk=pk)
        if opts.order_insertion_by:
            qs = qs.order_by(*opts.order_insertion_by)
        child_ids = qs.values_list('pk', flat=True)

        for child_id in child_ids:
            right = self._rebuild_helper(child_id, right, tree_id, level + 1)

        qs = self.model._default_manager.filter(pk=pk)
        self._mptt_update(qs,
            left=left,
            right=right,
            level=level,
            tree_id=tree_id
        )

        return right + 1

    def _calculate_inter_tree_move_values(self, node, target, position):
        """
        Calculates values required when moving ``node`` relative to
        ``target`` as specified by ``position``.
        """
        left = getattr(node, self.get_left_attr())
        level = getattr(node, self.get_level_attr())
        target_left = getattr(target, self.get_left_attr())
        target_right = getattr(target, self.get_right_attr())
        target_level = getattr(target, self.get_level_attr())

        if position == 'last-child' or position == 'first-child':
            if position == 'last-child':
                space_target = target_right - 1
            else:
                space_target = target_left
            level_change = level - target_level - 1
            parent = target
        elif position == 'left' or position == 'right':
            if position == 'left':
                space_target = target_left - 1
            else:
                space_target = target_right
            level_change = level - target_level
            parent = getattr(target, self.get_parent_attr())
        else:
            raise ValueError(_('An invalid position was given: %s.') % position)

        left_right_change = left - space_target - 1

        right_shift = 0
        if parent:
            right_shift = 2 * (node.get_descendant_count() + 1)

        return space_target, level_change, left_right_change, parent, right_shift

    def _close_gap(self, size, target, tree_id):
        """
        Closes a gap of a certain ``size`` after the given ``target``
        point in the tree identified by ``tree_id``.
        """
        self._manage_space(-size, target, tree_id, )

    def _create_space(self, size, target, tree_id):
        """
        Creates a space of a certain ``size`` after the given ``target``
        point in the tree identified by ``tree_id``.
        """
        self._manage_space(size, target, tree_id, )

    def _create_tree_space(self, target_tree_id):
        """
        Creates space for a new tree by incrementing all tree ids
        greater than ``target_tree_id``.
        """
        qs = self._mptt_filter(tree_id__gt=target_tree_id)
        self._mptt_update(qs, tree_id=F(self.get_tree_id_attr()) + 1)

    def _get_next_tree_id(self):
        """
        Determines the next largest unused tree id for the tree managed
        by this manager.
        """
        qs = self.get_query_set()
        max_tree_id = qs.aggregate(Max(self.get_tree_id_attr())).values()[0]

        max_tree_id = max_tree_id or 0
        return max_tree_id + 1

    def _inter_tree_move_and_close_gap(self, node, level_change,
            left_right_change, new_tree_id,
            parent_pk=None):
        """
        Removes ``node`` from its current tree, with the given set of
        changes being applied to ``node`` and its descendants, closing
        the gap left by moving ``node`` as it does so.

        If ``parent_pk`` is ``None``, this indicates that ``node`` is
        being moved to a brand new tree as its root node, and will thus
        have its parent field set to ``NULL``. Otherwise, ``node`` will
        have ``parent_pk`` set for its parent field.
        """
        opts = self.model._meta
        inter_tree_move_query = """
        UPDATE %(table)s
        SET %(level)s = CASE
                WHEN %(left)s >= %%s AND %(left)s <= %%s
                    THEN %(level)s - %%s
                ELSE %(level)s END,
            %(tree_id)s = CASE
                WHEN %(left)s >= %%s AND %(left)s <= %%s
                    THEN %%s
                ELSE %(tree_id)s END,
            %(left)s = CASE
                WHEN %(left)s >= %%s AND %(left)s <= %%s
                    THEN %(left)s - %%s
                WHEN %(left)s > %%s
                    THEN %(left)s - %%s
                ELSE %(left)s END,
            %(right)s = CASE
                WHEN %(right)s >= %%s AND %(right)s <= %%s
                    THEN %(right)s - %%s
                WHEN %(right)s > %%s
                    THEN %(right)s - %%s
                ELSE %(right)s END,
            %(parent)s = CASE
                WHEN %(pk)s = %%s
                    THEN %(new_parent)s
                ELSE %(parent)s END
        WHERE %(tree_id)s = %%s""" % {
            'table': qn(self.tree_model._meta.db_table),
            'level': qn(opts.get_field(self.get_level_attr()).column),
            'left': qn(opts.get_field(self.get_left_attr()).column),
            'tree_id': qn(opts.get_field(self.get_tree_id_attr()).column),
            'right': qn(opts.get_field(self.get_right_attr()).column),
            'parent': qn(opts.get_field(self.get_parent_attr()).column),
            'pk': qn(opts.pk.column),
            'new_parent': parent_pk is None and 'NULL' or '%s',
        }

        left = getattr(node, self.get_left_attr())
        right = getattr(node, self.get_right_attr())
        gap_size = right - left + 1
        gap_target_left = left - 1
        params = [
            left, right, level_change,
            left, right, new_tree_id,
            left, right, left_right_change,
            gap_target_left, gap_size,
            left, right, left_right_change,
            gap_target_left, gap_size,
            node.pk,
            getattr(node, self.get_tree_id_attr())
        ]
        if parent_pk is not None:
            params.insert(-1, parent_pk)

        cursor = self._get_connection(node).cursor()

        cursor.execute(inter_tree_move_query, params)

    def _make_child_root_node(self, node, new_tree_id=None):
        """
        Removes ``node`` from its tree, making it the root node of a new
        tree.

        If ``new_tree_id`` is not specified a new tree id will be
        generated.

        ``node`` will be modified to reflect its new tree state in the
        database.
        """
        left = getattr(node, self.get_left_attr())
        right = getattr(node, self.get_right_attr())
        level = getattr(node, self.get_level_attr())
        if not new_tree_id:
            new_tree_id = self._get_next_tree_id()
        left_right_change = left - 1

        self._inter_tree_move_and_close_gap(node, level, left_right_change,
            new_tree_id, )

        # Update the node to be consistent with the updated
        # tree in the database.
        setattr(node, self.get_left_attr(), left - left_right_change)
        setattr(node, self.get_right_attr(), right - left_right_change)
        setattr(node, self.get_level_attr(), 0)
        setattr(node, self.get_tree_id_attr(), new_tree_id)
        setattr(node, self.get_parent_attr(), None)
        node._mptt_cached_fields[self.get_parent_attr()] = None

    def _make_sibling_of_root_node(self, node, target, position):
        """
        Moves ``node``, making it a sibling of the given ``target`` root
        node as specified by ``position``.

        ``node`` will be modified to reflect its new tree state in the
        database.

        Since we use tree ids to reduce the number of rows affected by
        tree mangement during insertion and deletion, root nodes are not
        true siblings; thus, making an item a sibling of a root node is
        a special case which involves shuffling tree ids around.
        """
        if node == target:
            raise InvalidMove(_('A node may not be made a sibling of itself.'))

        opts = self.model._meta
        tree_id = getattr(node, self.get_tree_id_attr())
        target_tree_id = getattr(target, self.get_tree_id_attr())

        if node.is_child_node():
            if position == 'left':
                space_target = target_tree_id - 1
                new_tree_id = target_tree_id
            elif position == 'right':
                space_target = target_tree_id
                new_tree_id = target_tree_id + 1
            else:
                raise ValueError(_('An invalid position was given: %s.') % position)

            self._create_tree_space(space_target, )
            if tree_id > space_target:
                # The node's tree id has been incremented in the
                # database - this change must be reflected in the node
                # object for the method call below to operate on the
                # correct tree.
                setattr(node, self.get_tree_id_attr(), tree_id + 1)
            self._make_child_root_node(node, new_tree_id, )
        else:
            if position == 'left':
                if target_tree_id > tree_id:
                    left_sibling = target.get_previous_sibling()
                    if node == left_sibling:
                        return
                    new_tree_id = getattr(left_sibling, self.get_tree_id_attr())
                    lower_bound, upper_bound = tree_id, new_tree_id
                    shift = -1
                else:
                    new_tree_id = target_tree_id
                    lower_bound, upper_bound = new_tree_id, tree_id
                    shift = 1
            elif position == 'right':
                if target_tree_id > tree_id:
                    new_tree_id = target_tree_id
                    lower_bound, upper_bound = tree_id, target_tree_id
                    shift = -1
                else:
                    right_sibling = target.get_next_sibling()
                    if node == right_sibling:
                        return
                    new_tree_id = getattr(right_sibling, self.get_tree_id_attr())
                    lower_bound, upper_bound = new_tree_id, tree_id
                    shift = 1
            else:
                raise ValueError(_('An invalid position was given: %s.') % position)

            root_sibling_query = """
            UPDATE %(table)s
            SET %(tree_id)s = CASE
                WHEN %(tree_id)s = %%s
                    THEN %%s
                ELSE %(tree_id)s + %%s END
            WHERE %(tree_id)s >= %%s AND %(tree_id)s <= %%s""" % {
                'table': qn(self.tree_model._meta.db_table),
                'tree_id': qn(opts.get_field(self.get_tree_id_attr()).column),
            }

            cursor = self._get_connection(node).cursor()
            cursor.execute(root_sibling_query, [tree_id, new_tree_id, shift,
                                                lower_bound, upper_bound])
            setattr(node, self.get_tree_id_attr(), new_tree_id)

    def _manage_space(self, size, target, tree_id):
        """
        Manages spaces in the tree identified by ``tree_id`` by changing
        the values of the left and right columns by ``size`` after the
        given ``target`` point.
        """
        opts = self.model._meta
        space_query = """
        UPDATE %(table)s
        SET %(left)s = CASE
                WHEN %(left)s > %%s
                    THEN %(left)s + %%s
                ELSE %(left)s END,
            %(right)s = CASE
                WHEN %(right)s > %%s
                    THEN %(right)s + %%s
                ELSE %(right)s END
        WHERE %(tree_id)s = %%s
          AND (%(left)s > %%s OR %(right)s > %%s)""" % {
            'table': qn(self.tree_model._meta.db_table),
            'left': qn(opts.get_field(self.get_left_attr()).column),
            'right': qn(opts.get_field(self.get_right_attr()).column),
            'tree_id': qn(opts.get_field(self.get_tree_id_attr()).column),
        }
        cursor = self._get_connection(self.model).cursor()
        cursor.execute(space_query, [target, size, target, size, tree_id,
                                     target, target])

    def _move_child_node(self, node, target, position):
        """
        Calls the appropriate method to move child node ``node``
        relative to the given ``target`` node as specified by
        ``position``.
        """
        tree_id = getattr(node, self.get_tree_id_attr())
        target_tree_id = getattr(target, self.get_tree_id_attr())

        if tree_id == target_tree_id:
            self._move_child_within_tree(node, target, position)
        else:
            self._move_child_to_new_tree(node, target, position)

    def _move_child_to_new_tree(self, node, target, position):
        """
        Moves child node ``node`` to a different tree, inserting it
        relative to the given ``target`` node in the new tree as
        specified by ``position``.

        ``node`` will be modified to reflect its new tree state in the
        database.
        """
        left = getattr(node, self.get_left_attr())
        right = getattr(node, self.get_right_attr())
        level = getattr(node, self.get_level_attr())
        new_tree_id = getattr(target, self.get_tree_id_attr())

        space_target, level_change, left_right_change, parent, new_parent_right = \
            self._calculate_inter_tree_move_values(node, target, position,)

        tree_width = right - left + 1

        # Make space for the subtree which will be moved
        self._create_space(tree_width, space_target, new_tree_id)
        # Move the subtree
        self._inter_tree_move_and_close_gap(node, level_change,
            left_right_change, new_tree_id, parent.pk, )

        # Update the node to be consistent with the updated
        # tree in the database.
        setattr(node, self.get_left_attr(), left - left_right_change)
        setattr(node, self.get_right_attr(), right - left_right_change)
        setattr(node, self.get_level_attr(), level - level_change)
        setattr(node, self.get_tree_id_attr(), new_tree_id)
        setattr(node, self.get_parent_attr(), parent)

        node._mptt_cached_fields[self.get_parent_attr()] = parent.pk

    def _move_child_within_tree(self, node, target, position):
        """
        Moves child node ``node`` within its current tree relative to
        the given ``target`` node as specified by ``position``.

        ``node`` will be modified to reflect its new tree state in the
        database.
        """
        left = getattr(node, self.get_left_attr())
        right = getattr(node, self.get_right_attr())
        level = getattr(node, self.get_level_attr())
        width = right - left + 1
        tree_id = getattr(node, self.get_tree_id_attr())
        target_left = getattr(target, self.get_left_attr())
        target_right = getattr(target, self.get_right_attr())
        target_level = getattr(target, self.get_level_attr())

        if position == 'last-child' or position == 'first-child':
            if node == target:
                raise InvalidMove(_('A node may not be made a child of itself.'))
            elif left < target_left < right:
                raise InvalidMove(_('A node may not be made a child of any of its descendants.'))
            if position == 'last-child':
                if target_right > right:
                    new_left = target_right - width
                    new_right = target_right - 1
                else:
                    new_left = target_right
                    new_right = target_right + width - 1
            else:
                if target_left > left:
                    new_left = target_left - width + 1
                    new_right = target_left
                else:
                    new_left = target_left + 1
                    new_right = target_left + width
            level_change = level - target_level - 1
            parent = target
        elif position == 'left' or position == 'right':
            if node == target:
                raise InvalidMove(_('A node may not be made a sibling of itself.'))
            elif left < target_left < right:
                raise InvalidMove(_('A node may not be made a sibling of any of its descendants.'))
            if position == 'left':
                if target_left > left:
                    new_left = target_left - width
                    new_right = target_left - 1
                else:
                    new_left = target_left
                    new_right = target_left + width - 1
            else:
                if target_right > right:
                    new_left = target_right - width + 1
                    new_right = target_right
                else:
                    new_left = target_right + 1
                    new_right = target_right + width
            level_change = level - target_level
            parent = getattr(target, self.get_parent_attr())
        else:
            raise ValueError(_('An invalid position was given: %s.') % position)

        left_boundary = min(left, new_left)
        right_boundary = max(right, new_right)
        left_right_change = new_left - left
        gap_size = width
        if left_right_change > 0:
            gap_size = -gap_size

        opts = self.model._meta
        # The level update must come before the left update to keep
        # MySQL happy - left seems to refer to the updated value
        # immediately after its update has been specified in the query
        # with MySQL, but not with SQLite or Postgres.
        move_subtree_query = """
        UPDATE %(table)s
        SET %(level)s = CASE
                WHEN %(left)s >= %%s AND %(left)s <= %%s
                  THEN %(level)s - %%s
                ELSE %(level)s END,
            %(left)s = CASE
                WHEN %(left)s >= %%s AND %(left)s <= %%s
                  THEN %(left)s + %%s
                WHEN %(left)s >= %%s AND %(left)s <= %%s
                  THEN %(left)s + %%s
                ELSE %(left)s END,
            %(right)s = CASE
                WHEN %(right)s >= %%s AND %(right)s <= %%s
                  THEN %(right)s + %%s
                WHEN %(right)s >= %%s AND %(right)s <= %%s
                  THEN %(right)s + %%s
                ELSE %(right)s END,
            %(parent)s = CASE
                WHEN %(pk)s = %%s
                  THEN %%s
                ELSE %(parent)s END
        WHERE %(tree_id)s = %%s""" % {
            'table': qn(self.tree_model._meta.db_table),
            'level': qn(opts.get_field(self.get_level_attr()).column),
            'left': qn(opts.get_field(self.get_left_attr()).column),
            'right': qn(opts.get_field(self.get_right_attr()).column),
            'parent': qn(opts.get_field(self.get_parent_attr()).column),
            'pk': qn(opts.pk.column),
            'tree_id': qn(opts.get_field(self.get_tree_id_attr()).column),
        }

        cursor = self._get_connection(node).cursor()
        cursor.execute(move_subtree_query, [
            left, right, level_change,
            left, right, left_right_change,
            left_boundary, right_boundary, gap_size,
            left, right, left_right_change,
            left_boundary, right_boundary, gap_size,
            node.pk, parent.pk,
            tree_id])

        # Update the node to be consistent with the updated
        # tree in the database.
        setattr(node, self.get_left_attr(), new_left)
        setattr(node, self.get_right_attr(), new_right)
        setattr(node, self.get_level_attr(), level - level_change)
        setattr(node, self.get_parent_attr(), parent)
        node._mptt_cached_fields[self.get_parent_attr()] = parent.pk

    def _move_root_node(self, node, target, position):
        """
        Moves root node``node`` to a different tree, inserting it
        relative to the given ``target`` node as specified by
        ``position``.

        ``node`` will be modified to reflect its new tree state in the
        database.
        """
        left = getattr(node, self.get_left_attr())
        right = getattr(node, self.get_right_attr())
        level = getattr(node, self.get_level_attr())
        tree_id = getattr(node, self.get_tree_id_attr())
        new_tree_id = getattr(target, self.get_tree_id_attr())
        width = right - left + 1

        if node == target:
            raise InvalidMove(_('A node may not be made a child of itself.'))
        elif tree_id == new_tree_id:
            raise InvalidMove(_('A node may not be made a child of any of its descendants.'))

        space_target, level_change, left_right_change, parent, right_shift = \
            self._calculate_inter_tree_move_values(node, target, position,)

        # Create space for the tree which will be inserted
        self._create_space(width, space_target, new_tree_id)

        # Move the root node, making it a child node
        opts = self.model._meta
        move_tree_query = """
        UPDATE %(table)s
        SET %(level)s = %(level)s - %%s,
            %(left)s = %(left)s - %%s,
            %(right)s = %(right)s - %%s,
            %(tree_id)s = %%s,
            %(parent)s = CASE
                WHEN %(pk)s = %%s
                    THEN %%s
                ELSE %(parent)s END
        WHERE %(left)s >= %%s AND %(left)s <= %%s
          AND %(tree_id)s = %%s""" % {
            'table': qn(self.tree_model._meta.db_table),
            'level': qn(opts.get_field(self.get_level_attr()).column),
            'left': qn(opts.get_field(self.get_left_attr()).column),
            'right': qn(opts.get_field(self.get_right_attr()).column),
            'tree_id': qn(opts.get_field(self.get_tree_id_attr()).column),
            'parent': qn(opts.get_field(self.get_parent_attr()).column),
            'pk': qn(opts.pk.column),
        }

        cursor = self._get_connection(node).cursor()
        cursor.execute(move_tree_query, [level_change, left_right_change,
            left_right_change, new_tree_id, node.pk, parent.pk, left, right,
            tree_id])

        # Update the former root node to be consistent with the updated
        # tree in the database.
        setattr(node, self.get_left_attr(), left - left_right_change)
        setattr(node, self.get_right_attr(), right - left_right_change)
        setattr(node, self.get_level_attr(), level - level_change)
        setattr(node, self.get_tree_id_attr(), new_tree_id)
        setattr(node, self.get_parent_attr(), parent)
        node._mptt_cached_fields[self.get_parent_attr()] = parent.pk

redpajama_set_name: RedPajamaGithub


text:
package org.example.entity;

/**
 * A class with location outside "io.agrest" package. Used in tests of package-based resolvers.
 *
 * @see io.agrest.entity.AgP1
 */
public class NonAgP1 {
}


Investing in your home and its exterior is so much easier with GenStone luxury stone veneer. GenStone offers a collection of rock siding products that emulate the texture and appearance of natural stone but is superior in durability. Each panel is crafted of materials that will not falter or crack when exposed to the elements. GenStone panels are easy to install, enabling homeowners to save nearly half the cost of traditional masonry work.
GenStone Random Rock veneer features a combination of different-sized square rocks arranged in a unique pattern. Random Rock comes in a variety of colors, including Iron Ore, a deep, rich gray that contains hints of a softer gray throughout. This veneer would easily add drama and interest to any exterior.