forked from bjorntrondsen/activerecord-sqlanywhere-adapter
-
Notifications
You must be signed in to change notification settings - Fork 1
Jdbc #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
in4systems
wants to merge
48
commits into
clst:rails32
Choose a base branch
from
in4systems:jdbc
base: rails32
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Jdbc #2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
…ke '%01%' or something.
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
…isn't set Assuming it has been installed to /opt/sqlanywhere(11/12)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.