Part of the problem with migration is the incompatibilities that exist
between Lucee and ACF. Some of these incompatibilities seem to be
intentional, and sometimes when they are noticed Lucee devs just say,
“Yep, but our way is better.” The incompatibilities make migration
more difficult than it should be, and that holds people back. If
migration was simple, we would likely see more people make the transition.
I have heard this a number of times but I have no idea what
incompatibilities they are talking about that aren’t already documented.
If you are using client side stuff in your CF code then there are better
ways of handling that. Things like cfinput, cfselect, etc. I found using
JQuery better suited. For PDF stuff I jumped shipped from cfducment after
the first go around. Flying Saucer handles PDF stuff better.
Andrew PenhorwoodOn Thursday, June 11, 2015 at 11:05:39 AM UTC-4, Mike Henson wrote:
Part of the problem with migration is the incompatibilities that exist
between Lucee and ACF. Some of these incompatibilities seem to be
intentional, and sometimes when they are noticed Lucee devs just say, “Yep,
but our way is better.” The incompatibilities make migration more difficult
than it should be, and that holds people back. If migration was simple, we
would likely see more people make the transition.
I don’t use the ‘client side stuff.’ I generally don’t even use the cfm
extension. HTML and JavaScript on the client side, CFML server side. Like I
said earlier, I don’t have any ready examples. I made the migration from
ACF to Railo a while back, and was an early adopter of Lucee. We still have
quite a bit of legacy code running on ACF 8 (for internal use only), but I
wouldn’t expect a smooth transition from ACF 8 to anything current.On Thursday, June 11, 2015 at 11:14:38 AM UTC-5, Andrew Penhorwood wrote:
I have heard this a number of times but I have no idea what
incompatibilities they are talking about that aren’t already documented.
If you are using client side stuff in your CF code then there are better
ways of handling that. Things like cfinput, cfselect, etc. I found using
JQuery better suited. For PDF stuff I jumped shipped from cfducment after
the first go around. Flying Saucer handles PDF stuff better.
Andrew Penhorwood
On Thursday, June 11, 2015 at 11:05:39 AM UTC-4, Mike Henson wrote:
Part of the problem with migration is the incompatibilities that exist
between Lucee and ACF. Some of these incompatibilities seem to be
intentional, and sometimes when they are noticed Lucee devs just say, “Yep,
but our way is better.” The incompatibilities make migration more difficult
than it should be, and that holds people back. If migration was simple, we
would likely see more people make the transition.
Come on, Adam. Everyone knows the proper answer is 42.On Saturday, June 6, 2015 at 4:58:25 AM UTC-5, Adam Cameron wrote:
On Saturday, 6 June 2015 10:27:56 UTC+1, Robert Munn wrote:
Speaking of these issues with Lucee and CFML, editors, etc., does anyone
have any market intelligence on roughly how many day to day CFML developers
there are out there?
It’s 37. 38 if you count that bloke still doing OpenBD.
Come on, Adam. Everyone knows the proper answer is 42.
No-one in their right mind would ever think CFML is the answer to life, the
universe and everything ;-)On Saturday, 13 June 2015 00:23:20 UTC+1, Shawn Oden wrote:
Or in this case after 42 seconds…Sent from my iPhone
On Jun 13, 2015, at 8:19 AM, Adam Cameron <@Adam_Cameron> wrote:
On Saturday, 13 June 2015 13:15:34 UTC+1, AJ Mercer wrote:
Maybe if they installed CFML on Deep Thought it would not have taken seven and a half million years to calculated the answer
I recently spoke with a senior developer about a completely unrelated
position. He knew of ColdFusion, he saw it on my resume, and when he asked
me about it, he asked me what my front-end developer skills were like “since
CF is a front-end language”. THAT is the misperception that we are
dealing with in this language. And unfortunately, Adobe isn’t really doing
much to help with that poor impression of what the language is really good
at. Can it do it? Absolutely. And that’s part of what makes it an
interesting language in my opinion. I don’t need 10 different dependencies
to build a good application from front to back and connect to a pretty wide
range of databases in almost no time at all. Now that doesn’t mean that I SHOULD be building an entire site in ColdFusion. But the fact that I can
do it is sometimes helpful.
Anyway, I still say the language needs to go back to focusing on its roots:
making hard stuff easy. There are a bazillion ways to do any of the UI
stuff, which several people on this board have already taken their time to
demonstrate. We don’t need any more CF_BUZZWORDs in this language that end
up not getting used.
Maybe if they installed CFML on Deep Thought it would not have taken seven
and a half million years to calculated the answerOn Saturday, 13 June 2015, Adam Cameron <@Adam_Cameron> wrote:
On Saturday, 13 June 2015 00:23:20 UTC+1, Shawn Oden wrote:
Come on, Adam. Everyone knows the proper answer is 42.
No-one in their right mind would ever think CFML is the answer to life,
the universe and everything
I’m singing the praises of using stored procedures in cfscript.On Thursday, June 11, 2015 at 5:53:22 PM UTC-4, Steven Durette wrote:
How about this one. The CFScript version of cfstoredproc. Write code to
run on Railo but had to make it ACF compatible so I had to change all my
beautiful CFScript to tags.
Sent from my iPhone
On Jun 11, 2015, at 2:22 PM, Mike Henson <mike.he...@gmail.com <javascript:>> wrote:
Sorry, I don’t have any examples right now.
On Thu, Jun 11, 2015 at 11:38 AM, Julian Halliwell <julianh...@gmail.com <javascript:>> wrote:
I blogged many of the issues I encountered migrating from ACF9 to
Railo (which I did just before it became Lucee).
I never embraced the UI component in CF, as I found them always too limited
and requiring more code to work correctly while bringing too much
dependencies. And if you check ACF11 from the main CF house Adobe and see
the bloatware shipped over mobile, what we can do? or say?
I love CF since it did ALL what I wanted even if in the old times CF 4.5 or
5.0 crashes were a pain once you start to push it a little but the
language, logic, syntax, simplicity was ahead of the time. Since macromedia
take over we ve seen some improvements but few. Hopefully we got railo
project, as it offered it offered an open source solution community driven.
I got many dev’s who abandonneed CF mainly as there is less demand for it
and currently in my area you sell CF dev only in 2 cases:
maintenance for existing CF dev’s ( and some time customers are
preparing the shift for another plateforms as they feel abandonned and no
more dev’s).
You have a new project without language requirement hardcoded in the
specs and the customer will look for result rather than the tools.
We can’t ignore too that .net have evolved well and they finally understood
that bloatware UI are not the solutions and offer more support for open
standards or more clean MVC support. CF is more facing tought competition
from .net rather than nodeJS, also CF didn’t bank the JAVA roots to push
more the big java community to embrace it.On Saturday, June 13, 2015 at 2:18:12 AM UTC+2, Shawn Oden wrote:
I recently spoke with a senior developer about a completely unrelated
position. He knew of ColdFusion, he saw it on my resume, and when he asked
me about it, he asked me what my front-end developer skills were like “since
CF is a front-end language”. THAT is the misperception that we are
dealing with in this language. And unfortunately, Adobe isn’t really doing
much to help with that poor impression of what the language is really good
at. Can it do it? Absolutely. And that’s part of what makes it an
interesting language in my opinion. I don’t need 10 different dependencies
to build a good application from front to back and connect to a pretty wide
range of databases in almost no time at all. Now that doesn’t mean that I SHOULD be building an entire site in ColdFusion. But the fact that I can
do it is sometimes helpful.
Anyway, I still say the language needs to go back to focusing on its
roots: making hard stuff easy. There are a bazillion ways to do any of the
UI stuff, which several people on this board have already taken their time
to demonstrate. We don’t need any more CF_BUZZWORDs in this language that
end up not getting used.
OK, let me ask a stupid question but has been bugging me for a very long
time:
If you wanted to do:
SELECT * FROM Table1
in one of these newer languages, how would you do it?On Tue, Jun 16, 2015 at 3:17 AM, Mehdi B <@Mehdi_B> wrote:
I never embraced the UI component in CF, as I found them always too
limited and requiring more code to work correctly while bringing too much
dependencies. And if you check ACF11 from the main CF house Adobe and see
the bloatware shipped over mobile, what we can do? or say?
I love CF since it did ALL what I wanted even if in the old times CF 4.5
or 5.0 crashes were a pain once you start to push it a little but the
language, logic, syntax, simplicity was ahead of the time. Since macromedia
take over we ve seen some improvements but few. Hopefully we got railo
project, as it offered it offered an open source solution community driven.
I got many dev’s who abandonneed CF mainly as there is less demand for it
and currently in my area you sell CF dev only in 2 cases:
maintenance for existing CF dev’s ( and some time customers are
preparing the shift for another plateforms as they feel abandonned and no
more dev’s).
You have a new project without language requirement hardcoded in the
specs and the customer will look for result rather than the tools.
We can’t ignore too that .net have evolved well and they finally
understood that bloatware UI are not the solutions and offer more support
for open standards or more clean MVC support. CF is more facing tought
competition from .net rather than nodeJS, also CF didn’t bank the JAVA
roots to push more the big java community to embrace it.
On Saturday, June 13, 2015 at 2:18:12 AM UTC+2, Shawn Oden wrote:
I recently spoke with a senior developer about a completely unrelated
position. He knew of ColdFusion, he saw it on my resume, and when he asked
me about it, he asked me what my front-end developer skills were like “since
CF is a front-end language”. THAT is the misperception that we are
dealing with in this language. And unfortunately, Adobe isn’t really doing
much to help with that poor impression of what the language is really good
at. Can it do it? Absolutely. And that’s part of what makes it an
interesting language in my opinion. I don’t need 10 different dependencies
to build a good application from front to back and connect to a pretty wide
range of databases in almost no time at all. Now that doesn’t mean that I SHOULD be building an entire site in ColdFusion. But the fact that I can
do it is sometimes helpful.
Anyway, I still say the language needs to go back to focusing on its
roots: making hard stuff easy. There are a bazillion ways to do any of the
UI stuff, which several people on this board have already taken their time
to demonstrate. We don’t need any more CF_BUZZWORDs in this language that
end up not getting used.
I guess that’s why I’ve never bothered to post it as a question on
stackoverflow.
Afraid of getting downvoted like so many of my questions do.
But I know the people in the cf community are a kinder, gentler people.
It’s reasonable advice, and I did test it before suggesting it. You
made no indication of having tried to do anything to answer your own
question before asking it, so I figured an answer with about as much effort
was probably appropriate. Also as it’s completely off-topic for this forum,
I wanted to keep it short. And, yes, dismissive.
But here we are again.
I did not know the answer to your question, so I googled “python execute
sql statement” (I picked Python at random: it was the first language to pop
into my head), and all the matches pretty much gave the answer. Try it.
This is the first
match: Python - MySQL Database Access
I’m now going to google “groovy execute sql statement”. Again… the very
first link explains
it: Sql (Groovy 4.0.10)
How about Go? “golang execute sql statement”. The first link is the API. At
the top of that there’s a link to
here: SQLInterface · golang/go Wiki · GitHub. Examples.
Ruby? Second link goes to a stackOverflow question entitled “How do you
manually execute SQL commands in Ruby On …”, and the marked answer has an
example. It’s specific to a DB vendor, but you get the idea. And bear in
mind I stopped at the second answer… there might be a better answer
further down the page.
[etc]
So you’re interested in node.js. For the same search except for node.js the
fourth match (“fourth” chosen arbitrarily)
So this raises another issue. Let’s say we all want to promote CFML:
Q: Should I add CFML as an option at the bottom of the page, or should I
add Adobe ColdFusion or Lucee?On Wed, Jun 17, 2015 at 5:09 PM, Judith Barnett <@Judith_Barnett> wrote:
SELECT from Table1 is SQL, not any of the other languages, and the
correct syntax is SELECT fieldname(s) from table1.
Doing this is any language requires setting up a database connection,
and passing information to it. The syntax varies but it is not
necessarily any harder to this in any language as it in CFML - which
requires a datasource and a query.
i write in a lot of languages and my methodology for doing queries is
pretty much the same. Define the connection, build the query string,
pass the query string to the database and handle the results.
Productivity increases greatly when the focus is on building and using
algorithms and functions correctly instead of on syntax. You can
always look up the syntax.
On Tue, Jun 16, 2015 at 1:48 PM, Phillip Senn <@Phillip_Senn> wrote:
OK, let me ask a stupid question but has been bugging me for a very long
time:
If you wanted to do:
SELECT * FROM Table1
in one of these newer languages, how would you do it?
On Tue, Jun 16, 2015 at 3:17 AM, Mehdi B <@Mehdi_B> wrote:
I never embraced the UI component in CF, as I found them always too
limited and requiring more code to work correctly while bringing too
much
dependencies. And if you check ACF11 from the main CF house Adobe and
see
the bloatware shipped over mobile, what we can do? or say?
I love CF since it did ALL what I wanted even if in the old times CF 4.5
or 5.0 crashes were a pain once you start to push it a little but the
language, logic, syntax, simplicity was ahead of the time. Since
macromedia
take over we ve seen some improvements but few. Hopefully we got railo
project, as it offered it offered an open source solution community
driven.
I got many dev’s who abandonneed CF mainly as there is less demand for
it
and currently in my area you sell CF dev only in 2 cases:
maintenance for existing CF dev’s ( and some time customers are
preparing the shift for another plateforms as they feel abandonned and
no
more dev’s).
You have a new project without language requirement hardcoded in the
specs and the customer will look for result rather than the tools.
We can’t ignore too that .net have evolved well and they finally
understood that bloatware UI are not the solutions and offer more
support
for open standards or more clean MVC support. CF is more facing tought
competition from .net rather than nodeJS, also CF didn’t bank the JAVA
roots
to push more the big java community to embrace it.
On Saturday, June 13, 2015 at 2:18:12 AM UTC+2, Shawn Oden wrote:
I recently spoke with a senior developer about a completely unrelated
position. He knew of ColdFusion, he saw it on my resume, and when he
asked
me about it, he asked me what my front-end developer skills were like
“since
CF is a front-end language”. THAT is the misperception that we are
dealing
with in this language. And unfortunately, Adobe isn’t really doing
much to
help with that poor impression of what the language is really good at.
Can
it do it? Absolutely. And that’s part of what makes it an interesting
language in my opinion. I don’t need 10 different dependencies to
build a
good application from front to back and connect to a pretty wide range
of
databases in almost no time at all. Now that doesn’t mean that I SHOULD be
building an entire site in ColdFusion. But the fact that I can do it is
sometimes helpful.
Anyway, I still say the language needs to go back to focusing on its
roots: making hard stuff easy. There are a bazillion ways to do any of
the
UI stuff, which several people on this board have already taken their
time
to demonstrate. We don’t need any more CF_BUZZWORDs in this language
that
end up not getting used.
–
You received this message because you are subscribed to the Google Groups
“Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit
The problem here is that if you do some kind of self contained “how do I do SELECT * FROM BLA” it will look longer but a lot of these things are now handled by ORM’s or behind some kind of generator/service etc.
In meteor you use mongodb, but there is a package to use mysql. IT might not be as concise as CFML but the fact that it has full stack reactivity (i.e. if something changes in the db, all the clients are told about it and without reloading, they update) with meteor that you can’t do with CFML (yet) is a boon
For example Rails is not about doing SELECT * FROM People, it’s about doing (for example) Person.find() instead.
It’s still SELECT * FROM Table1, but in Coldfusion the datasource connection is configured at the server leve, and the methods are native. In NodeJS, for example, you need to add the library to connect to the specific database type. Example for MySQL:
npm install node-mysql
Then:
//You can always scope this part globally in your application, but this is the connection config.
var mysql = require(‘mysql’);
var db = mysql.createConnection({
host : ‘localhost’,
user : ‘root’,
password : ‘’,
database : ‘my_database’
});
db.connect();
db.query(‘SELECT * from Table1’, function(err, rows, fields) {
//if no error, do stuff with your query result rows
if (!err){
for(var i in rows){
console.log(rows[i]);
}
} else {
throw err;
};
});
connection.end();
It’s a different approach. PHP is the same way, but the connectivity modules are installed explicitly when installing the PHP packages (In PHP 5.6+, on many Linux distress, they’ve stopped including MySQL by default). It’s one of the ways in which CFML is a more integrated and mature language, as database connectivity is assumed at the application server level.
Update: I saw Mark posted pretty much the same thing when I was typing this so apologies for some duplication.
On June 17, 2015 at 11:18:17 AM, Phillip Senn (@Phillip_Sennmailto:Phillip_Senn) wrote:
That’s funny Adam.
I guess that’s why I’ve never bothered to post it as a question on stackoverflow.
Afraid of getting downvoted like so many of my questions do.
But I know the people in the cf community are a kinder, gentler people.
Seriously, how do you SELECT * FROM Table1 using any other web authoring programming language?
I looked at node.js for a little while but couldn’t understand how to do the same thing that cfquery does.
And I don’t think I want to jump from ColdFusion to php.
From the outside looking in, it looks like php is just another scripting language so why not stick with the one that I already know?
If anything, moving from cfquery to using stored procedures has moved most of my logic out of ColdFusion, so if I ever do decide to transition, there will certainly be less to do than there was a year ago.
On Tue, Jun 16, 2015 at 4:52 PM, Adam Cameron <@Adam_Cameron mailto:Adam_Cameron> wrote:
On 16 June 2015 at 21:48, Phillip Senn <@Phillip_Senn mailto:Phillip_Senn> wrote:
OK, let me ask a stupid question but has been bugging me for a very long time:
I’d focus less on this question and put effort into working out how to use google.
I guess that’s why I’ve never bothered to post it as a question on
stackoverflow.
Afraid of getting downvoted like so many of my questions do.
But I know the people in the cf community are a kinder, gentler people.
Seriously, how do you SELECT * FROM Table1 using any other web authoring
programming language?
I looked at node.js for a little while but couldn’t understand how to do
the same thing that cfquery does.
And I don’t think I want to jump from ColdFusion to php.
It really depends on the language, but for most of the ones I have worked
with you create a sql connection object, add the sql statement, and
execute. We can talk specifics to a language if you are interested in one
that I am familiar with.On Wed, Jun 17, 2015 at 10:18 AM, Phillip Senn <@Phillip_Senn> wrote:
That’s funny Adam.
I guess that’s why I’ve never bothered to post it as a question on
stackoverflow.
Afraid of getting downvoted like so many of my questions do.
But I know the people in the cf community are a kinder, gentler people.
Seriously, how do you SELECT * FROM Table1 using any other web authoring
programming language?
I looked at node.js for a little while but couldn’t understand how to do
the same thing that cfquery does.
And I don’t think I want to jump from ColdFusion to php.
From the outside looking in, it looks like php is just another scripting
language so why not stick with the one that I already know?
If anything, moving from cfquery to using stored procedures has moved most
of my logic out of ColdFusion, so if I ever do decide to transition, there
will certainly be less to do than there was a year ago.
On Tue, Jun 16, 2015 at 4:52 PM, Adam Cameron <@Adam_Cameron> wrote:
On 16 June 2015 at 21:48, Phillip Senn <@Phillip_Senn> wrote:
OK, let me ask a stupid question but has been bugging me for a very long
time:
I’d focus less on this question and put effort into working out how to
use google.
