Skip to content

Conversation

@in4systems
Copy link

No description provided.

Chris Couzens and others added 30 commits May 22, 2012 10:51
Imported savitri02@066b348

I'm not too familiar with git, so I'm not sure if I followed the correct patch import protocol here.
If there was ever a good reason to require limit and offset before we do distinct, someone should let me know.
Don't drop views when running db:test:purge.
…s, XML -> text, uniqueindetifier -> integer

Current patch to fix issue where all binaries are going in as long binary(limit), path to just dump as binary(limit) untill a perminant fix is created.
Why am I removing the whitespace from the end of the string?

Sqlanywhere allowed us to create a string foreign key.
Somehow on only one end of the foreign key, the values got spaces at the end.
The foreign key was still valid in Sqlanywhere: It worked for joins and it worked for referencing constraints.

It however does not work for the ActiveRecord includes method.
Rails will bring back the associated records, but then it fails to pair the records correctly.
Removing whitespace from the ends of all strings fixes this. It is a hack however, so I'm open
for suggestions on coming up with a better method.
and the same for False
Check that the table belongs to dba when getting the table_structure.
If 2 users had the same table name, we used to get the columns for both.
Sqlanywhere doesn't like groups being aliased.
This reverts commit 5e066d7.
This commit broke using the sqlanywhere gem
This reverts commit f1c954c.
It does seem to be working- no doubt I'll find a problem later on
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant