So you're using the nodejs modules express and jade, and you're posting some form data, and you can't work out why 'req.body' is undefined.
You've read the docs, and you're using app.use(express.bodyParser()) and its not working still.
You're config looks like this :
But you need it the other way round, like this :
What you've done wrong is have the bodyParser() line after the app.router line.
Make sure you put the bodyParser() line before the app.router line, and you're gravy.
Note that after a twitter exchange with the express developers, this isn't a bug, but a feature of express's middleware config - a side-effect of the flexibility of their middleware injection.
This 'fix' works for me - I'm pretty new to express, so I've no idea on the impact on other middleware you may have configured.
I'm sure after more playtime with express I'll understand why routing config blat's body parsing if done in that order.
PS - If anyone does know the answer, I'd welcome a full explanation, or link to the docs on it.
Friday, 27 January 2012
Wednesday, 25 January 2012
Nodejs Tedious Sql Server Driver and GUID / UNIQUEIDENTIFIER
So you're using SQL Server / SQLEXPRESS with nodejs for some odd reason, and you're trying to pull back Ids from a table that is has the field declared as UNIQUEIDENTIFIER, but you keeping getting an error like :
Unrecognised data type 0x24 at offset 0x0009
But its OK when you pull back nvarchar's etc.
Nasty hack that works (considering js doesn't know what a GUID is anyway) :
Change :
select Id from table
to:
select convert(varchar(38) , Id) from table
and all is well.
Unrecognised data type 0x24 at offset 0x0009
But its OK when you pull back nvarchar's etc.
Nasty hack that works (considering js doesn't know what a GUID is anyway) :
Change :
select Id from table
to:
select convert(varchar(38) , Id) from table
and all is well.
Subscribe to:
Posts (Atom)