eckyptang

47 ms·

1. 391.▲
   by eckyptang 14y ago

   That's hardly a great reference, especially when he immediately shot himself by not checking vendor limits... http://www.codinghorror.com/blog/2009/07/oh-you-wanted-aweso...
2. 392.▲
   by eckyptang 14y ago

   Looking at the way arrays are implemented, they can readily turn operations into O(M*N) rather than O(N). Even the PgSQL documentation suggests cases that will hurt you. I would suggest that the relational model is maintained as there are n
3. 393.▲
   by eckyptang 14y ago

   The more you put in the database black box, the more scalability problems you will encounter in the future. It's more economical to scale out than buy bigger databases servers. Please just don't do it.
4. 394.▲
   by eckyptang 14y ago

   Never tried the UNC hack. Might have a bash at that. The actual restriction is in the Win32 subsystem which has both C string and Unicode versions of API calls. Some API is hooked in via the C API which tends to use TCHAR var[MAX_PATH] as t
5. 395.▲
   by eckyptang 14y ago

   As a frequent user of the .Net stack, this sort of thing is common and very annoying indeed. I'd guess that it's probably using a temp path which is close to the length of the path limit on Windows and is either not handling it or truncatin