Freeform SQL

[Michael Workman]

I have been using an older version of dadabik and i just installed the newer version to see whats new

I used the freeform sql capability alot in the old version and really liked it. Especially nice if you want to create a drop down from other than key fields and where you want to do joins and such I dont see this capability now. Has it been removed? I cannot find it in the documentation. It used to consist of the keyword "sql:" followed by your code.xxxx

Would appreciate the help

 

[Eugenio]

Michael Workman wrote:

> I have been using an older version of dadabik and i just
> installed the newer version to see whats new
>
> I used the freeform sql capability alot in the old version
> and really liked it. Especially nice if you want to create a
> drop down from other than key fields and where you want to do
> joins and such I dont see this capability now. Has it been
> removed? I cannot find it in the documentation. It used to
> consist of the keyword "sql:" followed by your code.xxxx
>
> Would appreciate the help

Yes the function has been removed (at least for the moment) because it was difficult to integrate in the new primary/foreign key approach.
Could you provide an example in which you need that feature? Maybe it is possible to get the same result with DaDaBIK 3.0 exploiting the primary/foreign key feature.



(Latest version of DaDaBIK when this message was posted: 3.0 beta)

 

[Michael Workman]

Thanks for the response... but i had hoped it was there....and i had missed it.

It was a great feature... It allowed me to do things like this

Select* from authors, publishers where authors.city = publishers.city

It was nice because it allowed you to use the full sql to constrain a query... Even if it did not have primary keys I sure hope you can add it back...it made it really powerful.

Have you ever thought of allowing fields to be display only and not written back on insert... for example... it would be great to create hidden fields that would not be displayed but allow you to write them back out...based on a sql...where you could do adds and other manipulation through sql.

Great program...though...I appreciate your time and efforts. Let me know if i can help in any way. THANKS

 

[Eugenio]

Michael Workman wrote:

> Thanks for the response... but i had hoped it was
> there....and i had missed it.
>
> It was a great feature... It allowed me to do things like
> this
>
> Select* from authors, publishers where authors.city =
> publishers.city
>
> It was nice because it allowed you to use the full sql to
> constrain a query... Even if it did not have primary keys

Ok but you can get the same results with v3.0 if you define a primary key, and defining a primary key is a good practice

> I sure hope you can add it back...it made it really powerful.
>
> Have you ever thought of allowing fields to be display only
> and not written back on insert... for example... it would be
> great to create hidden fields that would not be displayed but
> allow you to write them back out...based on a sql...where you
> could do adds and other manipulation through sql.

Ok, if I have understand this is however a "feature request", it is not possible to get such a result, even with the freeform sql feature enabled.

> Great program...though...I appreciate your time and efforts.
> Let me know if i can help in any way.

You can of course support the DaDaBIK project by helping the support; a lot of support requests are posted on the forum every days and I don't have enough time to reply to all shortly.
If you are interested please contact me.



(Latest version of DaDaBIK when this message was posted: 3.0 beta)