kalechi crud

In response to: My Top 10 JavaScript/SSJS Mistakes

The whole XPages paradigm is so different to the normal web page / form / agent thinking. I find it hard when you have to go between @formula, Lotuscript, java and JavaScript in the same day.
I think the error checking should tell you more, so when you enter := it popups with a message "Hey stupid, this is JavaScript not @formulas!"

I can't wait till the AI release where you just tell it what you want and it figures out the code.

In response to: Help Wanted: Building A New Yellowverse

Not only is the community fragmented but the information is fragmented. A wiki is like a dictionary, it works if you know what you are looking for. There are some blogs that give a page that puts things together but are quickly outdated.

I would like to see an area on one of the current yellow sites, that is maintained and kept current. Things like a list of all admin tools with description & ratings, dev tools, tutorials by product/area, etc.
.

In response to: XPages... the Biggest Barrier

The biggest huddle will be the apps only work with 8.5.x. So until the costumer has upgrade the servers and clients (8.5.1), it's unusable. For a lot of my customers this means 2010. Also it means that customers train their developers, now I can get an web developer and notes developer together to build web pages that are nice. Not with xpages. It's not compatible with another code. you can't intermix an xpage and normal webpage or normal notes form. I think it has it's place but it's going to be a long time for it to be the Notes development standard. It's nice technology

Going further with db2 and Domino
This will be for those that want to do some fun development and get fast views.
Let me know if there is anything you would like to see in a demo

In response to: Struggling with NSFDB2

The directory is only entered if you have created the directory instead of letting Domino create it when it firsts starts up. Also only compact -B will impact the nsfdb2 database. There is now a -g & -G compact command for groups. For a size reduction all databases in a db2 group need to be compacted. If you use the the g commands the database are moved to a new group to reduce the storage used. G will do an entire group at one time, while g does just one database by moving it to a new group. Setting the group size to a smaller number will reduce the chance of corruption and speed compaction. I run with 5 nsf to a group, support has had us set it to 1 for a large heavily used app server.

In response to: nsfdb2 - Access view not updating in DB2?

The DAV actually builds links to the Domino data that is in db2. So if the view is not showing the updated doc, are the db2 tables being updated? Look at the DAV table in db22 to see if it's being updated. Also if fields on the doc are not the same format (date, text, number) as the DAV list them. they will not go. I spent more time cleaning up Notes data and change the current forms to be more restrictive then it took to build the db2 stuff. This is also for field size, if you have marked allow truncation then it will go but if not, Domino can't put 300 characters in to a field that supports 20. I found this with a phone number field, someone had enter 400 character about when to call instead of just the phone number.

I just finished setting up and testing the new Domino 8.5 beta with db2 v9.1 backend. It was the easiest install to date (after 5 or 6 it should be easy). In 8.5 all ods version can be convert to db2, with 8.0.1 only r7 (ods 43) would convert. I was able to get DAOS to run on the server, it just won't work with a db2 enabled database. But the other parameters work, design compression, data compression, lz1, etc. I haven't been able to see if they make a difference to the actual database size since it's split across many tables.

For testing I plan to see how db2 autoconfig and compacting help or impact the performance.
It makes a great way to build views for the web!  Now to test xPages and see if parameters can be passed to the query views to dynamically build the sql query