The Generic API

[AtW]

while(true)
{
DoPostOnCUK(GetRandomSockie(),”tulip tulip tulip”);
}

object F_uckWorking(string command, ...)

FTFY

[Mich the Tester]

FTFY

Thanks; always good to have a code review.

[minestrone]

Would you be talking about the inner platform like the enterprise rules engine would you.

I am working with one now that was meant to deal with every future bit of technology, really it boils down to a big feckin hashmap wrapped with 200,000 lines of code.

I though these were all written about 10 years ago when people never knew any better but I was actually working on one last year where the architect explained "yes, it sells train tickets but we really we designed it so it could sell anything at all". I knocked back the extension.

[TheFaQQer]

Oh dear, no wonder I've been going round in circles. I wanted to do a delete operation so naturally passed in "delete". Now I've finally located the relevant page in the documentation I see I should be passing in "delet". It was obviously put together by an illiterate.

So what you need is to write a wrapper that accepts "delete" and then calls the generic API with "delet". Simples.

[DimPrawn]

I worked with a guy designing a corporate database.

He had a plan that every table would have a many-to-many join table with every other, so the schema looked like a rats nest. He said this "future proofed" the database for any possible business changes.

Smart cookie.

[doodab]

I once worked with a piece of software that had two tables.

items (item_id, item_name)

attributes(attribute_id, item_id, attribute_name, attribute_value)

The software in question was an offering from a well known database vendor.

[TheFaQQer]

I once worked with a piece of software that had two tables.

items (item_id, item_name)

attributes(attribute_id, item_id, attribute_name, attribute_value)

The software in question was an offering from a well known database vendor.

You mean an Entity-Attribute-Value database.

Good theory, awful practise.

[AtW]

Good theory, awful practise.

Practice

[DimPrawn]

Practice

We don't pick you up on your Russian typo's so lay off our English ones.

[Mich the Tester]

I worked with a guy designing a corporate database.

He had a plan that every table would have a many-to-many join table with every other, so the schema looked like a rats nest. He said this "future proofed" the database for any possible business changes.

Smart cookie.

Was he from infosys?