18,443 reputation
43369
bio website in.another.dimension
location Athens, Greece
age 46
visits member for 3 years, 8 months
seen 2 hours ago

Interests: math, programming and games, not necessarily in that order.


2h
comment Retrieving month from date field in my database
Not really, it doesn't.
4h
revised Optimizing query - understanding explain
added 14 characters in body; edited title
4h
comment Optimizing query - understanding explain
Please add the query as well.
4h
reviewed No Action Needed Can I stop a SQL database backup after it has already started?
7h
reviewed Close Error when reorganizing the autonumber in Postgresql
9h
reviewed Close Is there a faster way to get UNION ALL behavior in Postgres?
10h
comment Oracle: Helping hand writing this query. Do I need a sub query here?
You probably get only some of the months because there are data for this customer only for these months (they did not order anything the other months.) Try making a SQLFiddle with a sample of rows so we can test.
10h
reviewed No Action Needed Getting 'specified network password is not correct' when trying to change password
10h
reviewed Close How do I select all child table records based on condition
10h
reviewed Reject suggested edit on The client need 'SUPER' privileges to the reports DB in order to create and maintain my Functions
10h
answered How do I select all child table records based on condition
22h
comment Using partitioned table, and dealing with auto_increment PK
You can still add a non-unique index on (id, datetime) so searching by id only is fast.
22h
comment Using partitioned table, and dealing with auto_increment PK
no, it doesn't. The restriction in MySQL's partitioning is there so every search with any primary or unique key should be able to search only one partition. So, if you want to partition by date, then your searches should not use ID alone but date+id or just date. The auto_increment will prevent any duplicates anyway (unless there are manual inserts or updates.) But the uniqueness on (id) will not be not strictly enforced, true.
22h
comment Using partitioned table, and dealing with auto_increment PK
Consider also make the pk (datetime, id)
22h
revised Doing a insert across two databases with same collations and getting an error
added 8 characters in body
23h
comment Doing a insert across two databases with same collations and getting an error
And the insert statement seems weird. Where is T1 defined?
23h
revised Doing a insert across two databases with same collations and getting an error
added 6 characters in body; edited tags; edited title
1d
reviewed No Action Needed How to store highly configurable relationships based on multiple conditions
1d
reviewed Close SQL Server Agent 2012 Job Schedule Report
1d
reviewed Close Peer to peer replication error