Set your LC_COLLATE environmental variable on the PG server (and any client machines). PG probably isn't finding a setting, so it's defaulting to "C". If you switch it to something like en_US, collation will be case-insensitive. You may have to reindex after making the change.
It's not correct, this bogus implementation is going to print the number if either side of the OR presents a remainder. It should print only if both sides present a remainder. It should be AND, not OR.
They are in Hollywood working in a visual medium. It shouldn't be a surprise that they would have an above-average concern in how they look and that they also might exchange visual information with each other with more ease than you or I might be accustomed to. That doesn't mean they want that information to travel beyond their peers.
BIRT is great but it's not a full BI suite. That said, we did select it here for reporting vs Pentaho's reporting. We have over 8,000 US locations generating reporting off of it daily and it works reliably with minimal issues.
And what you are seeing is a community of end users, who can all edit Google Maps directly, discussing how to best correct some POI data. How can I do this on Apple Maps? Apple will never be able to compete with Google. Most of the comparison between their mapping products so far is on cartography, the Denver airport is the first real mention of POI data (and a rare fail on Google's side). Thousands and thousands of businesses open and close each day in the US alone, Apple will never be able to keep up with the changes (much as Navteq and Garmin never have). Google can, because they crowdsource the information. It's classic cathedral vs bazaar.
Generally, the exact opposite is true - coming from mysql leaves you at a severe disadvantage. You'll struggle to understand basics like how to get a primary key in a row of data under PG or Ora. Just the fact that you're mentioning SQL and PLSQL as if they were interchangeable means you're clueless, it's like comparing TCP with PHP. Hint: PL/SQL is Oracle's name for their procedural language. Mysql's procedural language doesn't even have a name, yet it is just as incompatible with MSSQL, Oracle, Postgres, etc as they are with each other.
Just to pick the low hanging fruit, tell me how you get the current timestamp on mysql, postgres, and oracle in a database-agnostic way.
Most datacenter generators run on diesel. Onan doesn't even produce a NG or propane genset, Kohler's largest gas genset is 300kW, their largest diesel is 3,250kW. Cat's largest gas is 6,220kW, largest diesel is 17,460kW.
Are your clients willing to wait, with their sites offline, while you truck down to the datacenter to troubleshoot a server? Or did you expend resources to deploy a failover solution? How fast can you bring up 5 new boxes, imaged from another? Are your OS sessions virtualized, for when customer X wants to give their own admins root, or do you have to have separate hardware for those customers? There's so many extra costs, soft costs, and risks that don't seem to have been considered. If running your own hardware was bottom-line effective, there wouldn't be so much migration towards cloud solutions.
This needs modding up. After ten years of dealing with occasional hardware issues on colocated servers, I am more than happy to pay a small premium to let someone else worry about the metal, and to avoid those outages for my clients.
Cable ties cost next to nothing, hold the bundle much tighter than Velcro, and don't get dirty like Velcro does. In my home recording studio, the cables secured by velcro need too-frequent adjustment. The cables slide back and forth inside the bundle. The cable-tied bundles don't have this issue.
He sounds like our IT Director... no input on how anything actually works but always quick to critique the name of a new database field or function, color of a control, etc. Bikeshedding.
The reason it didn't have it from the start is probably due to the same factors that led to nearly all of the major exploit classes... no one thought of the issue that resulted in the exploits. If we start way back in the beginning ("Smashing the Stack for Fun and Profit") there just wasn't much consideration given to the idea that data could result in malicious code execution.
In addition, it seems like the discussions of Wikipedia's accuracy focus on 10% of the articles, probably the ones for which a person would be least inclined to use Wikipedia as the primary reference. This narrow scope, of course, is never mentioned.
With an expert-driven system, all of the little one-off articles on niche or regionally-localized subjects are going to be missing. I think that these are where Wikipedia's real value is, not in maintaining its article on "Israel".
Set your LC_COLLATE environmental variable on the PG server (and any client machines). PG probably isn't finding a setting, so it's defaulting to "C". If you switch it to something like en_US, collation will be case-insensitive. You may have to reindex after making the change.
It's not correct, this bogus implementation is going to print the number if either side of the OR presents a remainder. It should print only if both sides present a remainder. It should be AND, not OR.
They are in Hollywood working in a visual medium. It shouldn't be a surprise that they would have an above-average concern in how they look and that they also
might exchange visual information with each other with more ease than you or I might be accustomed to. That doesn't mean they want that information to travel beyond their peers.
BIRT is great but it's not a full BI suite. That said, we did select it here for reporting vs Pentaho's reporting. We have over 8,000 US locations generating reporting off of it daily and it works reliably with minimal issues.
If you don't know what ETL is you shouldn't be making any BI-related commentary. Also, stop using so many MS-specific acronyms.
And what you are seeing is a community of end users, who can all edit Google Maps directly, discussing how to best correct some POI data. How can I do this on Apple Maps? Apple will never be able to compete with Google. Most of the comparison between their mapping products so far is on cartography, the Denver airport is the first real mention of POI data (and a rare fail on Google's side). Thousands and thousands of businesses open and close each day in the US alone, Apple will never be able to keep up with the changes (much as Navteq and Garmin never have). Google can, because they crowdsource the information. It's classic cathedral vs bazaar.
Generally, the exact opposite is true - coming from mysql leaves you at a severe disadvantage. You'll struggle to understand basics like how to get a primary key in a row of data under PG or Ora. Just the fact that you're mentioning SQL and PLSQL as if they were interchangeable means you're clueless, it's like comparing TCP with PHP. Hint: PL/SQL is Oracle's name for their procedural language. Mysql's procedural language doesn't even have a name, yet it is just as incompatible with MSSQL, Oracle, Postgres, etc as they are with each other.
Just to pick the low hanging fruit, tell me how you get the current timestamp on mysql, postgres, and oracle in a database-agnostic way.
Most people stay away from the GPL because most people are not programmers.
Naming software versions by nicknames has been around since you were in diapers. Sorry that you are finally being exposed to it.
Just the fact that the fuel truck could even get to their facility says that they did not receive any significant weather.
Most datacenter generators run on diesel. Onan doesn't even produce a NG or propane genset, Kohler's largest gas genset is 300kW, their largest diesel is 3,250kW. Cat's largest gas is 6,220kW, largest diesel is 17,460kW.
Are your clients willing to wait, with their sites offline, while you truck down to the datacenter to troubleshoot a server? Or did you expend resources to deploy a failover solution? How fast can you bring up 5 new boxes, imaged from another? Are your OS sessions virtualized, for when customer X wants to give their own admins root, or do you have to have separate hardware for those customers? There's so many extra costs, soft costs, and risks that don't seem to have been considered. If running your own hardware was bottom-line effective, there wouldn't be so much migration towards cloud solutions.
This needs modding up. After ten years of dealing with occasional hardware issues on colocated servers, I am more than happy to pay a small premium to let someone else worry about the metal, and to avoid those outages for my clients.
Cable ties cost next to nothing, hold the bundle much tighter than Velcro, and don't get dirty like Velcro does. In my home recording studio, the cables secured by velcro need too-frequent adjustment. The cables slide back and forth inside the bundle. The cable-tied bundles don't have this issue.
I have a Windows Mobile 6 phone right now and what he says is exactly true.
Hopefully the levees surrounding Manhattan will hold...
Love the Previous Entry on that page...
He sounds like our IT Director... no input on how anything actually works but always quick to critique the name of a new database field or function, color of a control, etc. Bikeshedding.
I saw identical behavior when a script tried to create an array that was too large.
The reason it didn't have it from the start is probably due to the same factors that led to nearly all of the major exploit classes... no one thought of the issue that resulted in the exploits. If we start way back in the beginning ("Smashing the Stack for Fun and Profit") there just wasn't much consideration given to the idea that data could result in malicious code execution.
Using bound parameters, as the previous post suggested, is the correct way to mitigate SQL injection.
They do that in South Florida, the outflow goes into the ocean and they see how many fish will die.
Didn't this blogger commit a computer crime (at least in the US) by downloading the password file?
I use myspace fairly often and I think the issue is actually the Flash player (which is typically invoked ten trillion times on each myspace page).
In addition, it seems like the discussions of Wikipedia's accuracy focus on 10% of the articles, probably the ones for which a person would be least inclined to use Wikipedia as the primary reference. This narrow scope, of course, is never mentioned.
With an expert-driven system, all of the little one-off articles on niche or regionally-localized subjects are going to be missing. I think that these are where Wikipedia's real value is, not in maintaining its article on "Israel".