aahh now is more clear; you don't need only a ON clause with FK, you want add an AND clause to the JOIN ON.It is an unsupported feature and we have an open issue about it http://jira.nhibernate.org/browse/NH-514
BTW, as Gustavo said, you can use an SQL in NH-style http://nhforge.org/doc/nh/en/index.html#manipulatingdata-nativesql until we don't have the HQL-AST working. 2008/12/16 Gabriel Mancini de Campos <[email protected]> > > Hi Fabio > > thanks for your answer, how to i put this explicit in my criteria ?? > this is the SQL generate from NH. > > see in left outer join SalaTemp my problem.. > > > select > sala0_.Id as Id13_0_ > , salatemp3_.Id as Id20_1_ > , sala0_.Numero as Numero13_0_ > , sala0_.Digitando as Digitando13_0_ > , sala0_.Inicio as Inicio13_0_ > , sala0_.Fim as Fim13_0_ > , sala0_.Atendente_Id as Atendente6_13_0_ > , sala0_.Supervisor_Id as Supervisor7_13_0_ > , sala0_.Protocolo as Protocolo13_0_ > , sala0_.ProtocoloInterno as Protocol9_13_0_ > , sala0_.Comentario as Comentario13_0_ > , sala0_.chat_id as chat11_13_0_ > , sala0_.statusSala_id as statusSala12_13_0_ > , sala0_.atendido_id as atendido13_13_0_ > , sala0_.grauSatisfacao_id as grauSat14_13_0_ > , salatemp3_.Autor as Autor20_1_ > , salatemp3_.Frase as Frase20_1_ > , salatemp3_.Hora as Hora20_1_ > , salatemp3_.Reservado as Reservado20_1_ > , salatemp3_.sala_id as sala6_20_1_ > , salatemp3_.sala_id as sala6_0__ > , salatemp3_.Id as Id0__ > from > Sala sala0_ > inner join Chat chat1_ on sala0_.chat_id=chat1_.Id > inner join StatusSala statussala2_ on > sala0_.statusSala_id=statussala2_.Id > left outer join SalaTemp salatemp3_ on sala0_.Id=salatemp3_.sala_id > [ and salatemp3_.hora < 63365027317266 ] <- i need put this in my > criteria > where > ((statussala2_.Id=3 )or(statussala2_.Id=2 )) > and(chat1_.Id=742 ) > > > On 16 dez, 15:33, "Fabio Maulo" <[email protected]> wrote: > > Limitation? I know some RDBMS where put the clause in the WHERE of an > > implicit JOIN or in the ON of an explicit JOIN don't cause any kind of > > problems.BTW you can use an explicit join, in your query, if you want the > ON > > clause for FKs. > > > > 2008/12/16 Gabriel Mancini de Campos <[email protected]> > > > > > > > > > Hello to all, I am new to list, and sorry if my question is very > > > primary. > > > > > Guys, I found something very bad. see this: > > > if you need to create a channel find a model to generate a > > > SQL type: LEFT > > > OUTER JOIN ON (AND A.pk B.fk Some Field == Valo) <- this field is not > > > generated in the ON clause, but in WHERE, and I think this is a > > > limitation of NHibernate! > > > Does anyone have any idea how I can work around this problem? > > > > -- > > Fabio Maulo > > > -- Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
